[PATCH v4] powerpc: setup_64: set up PACA before parsing device tree

Currently, we set up the PACA after parsing the device tree for CPU features. Before that, r13 contains random data, which means there is random data in r13 while we're running the generic dt parsing code. This random data varies depending on whether we boot through a vmlinux or a zImage: for the

Re: [PATCHv3 2/2] pseries/scm: buffer pmem's bound addr in dt for kexec kernel

On 3/4/20 2:17 PM, Pingfan Liu wrote: At present, plpar_hcall(H_SCM_BIND_MEM, ...) takes a very long time, so if dumping to fsdax, it will take a very long time. that should be fixed by faa6d21153fd11e139dd880044521389b34a24f2 Author: Aneesh Kumar K.V AuthorDate: Tue Sep 3 18:04:52

Re: [PATCHv3 2/2] pseries/scm: buffer pmem's bound addr in dt for kexec kernel

Appreciate for your kind review. And I have some comment as below. On Fri, Mar 13, 2020 at 11:18 AM Oliver O'Halloran wrote: > > On Wed, Mar 4, 2020 at 7:50 PM Pingfan Liu wrote: > > > > At present, plpar_hcall(H_SCM_BIND_MEM, ...) takes a very long time, so > > if dumping to fsdax, it will

[PATCH AUTOSEL 4.4 2/7] powerpc: Include .BTF section

From: "Naveen N. Rao" [ Upstream commit cb0cc635c7a9fa8a3a0f75d4d896721819c63add ] Selecting CONFIG_DEBUG_INFO_BTF results in the below warning from ld: ld: warning: orphan section `.BTF' from `.btf.vmlinux.bin.o' being placed in section `.BTF' Include .BTF section in vmlinux explicitly to

[PATCH AUTOSEL 4.9 2/7] powerpc: Include .BTF section

From: "Naveen N. Rao" [ Upstream commit cb0cc635c7a9fa8a3a0f75d4d896721819c63add ] Selecting CONFIG_DEBUG_INFO_BTF results in the below warning from ld: ld: warning: orphan section `.BTF' from `.btf.vmlinux.bin.o' being placed in section `.BTF' Include .BTF section in vmlinux explicitly to

[PATCH AUTOSEL 4.14 03/15] powerpc: Include .BTF section

From: "Naveen N. Rao" [ Upstream commit cb0cc635c7a9fa8a3a0f75d4d896721819c63add ] Selecting CONFIG_DEBUG_INFO_BTF results in the below warning from ld: ld: warning: orphan section `.BTF' from `.btf.vmlinux.bin.o' being placed in section `.BTF' Include .BTF section in vmlinux explicitly to

[PATCH AUTOSEL 4.19 04/20] powerpc: Include .BTF section

From: "Naveen N. Rao" [ Upstream commit cb0cc635c7a9fa8a3a0f75d4d896721819c63add ] Selecting CONFIG_DEBUG_INFO_BTF results in the below warning from ld: ld: warning: orphan section `.BTF' from `.btf.vmlinux.bin.o' being placed in section `.BTF' Include .BTF section in vmlinux explicitly to

[PATCH AUTOSEL 5.4 10/35] powerpc: Include .BTF section

From: "Naveen N. Rao" [ Upstream commit cb0cc635c7a9fa8a3a0f75d4d896721819c63add ] Selecting CONFIG_DEBUG_INFO_BTF results in the below warning from ld: ld: warning: orphan section `.BTF' from `.btf.vmlinux.bin.o' being placed in section `.BTF' Include .BTF section in vmlinux explicitly to

[PATCH AUTOSEL 5.5 11/41] powerpc: Include .BTF section

From: "Naveen N. Rao" [ Upstream commit cb0cc635c7a9fa8a3a0f75d4d896721819c63add ] Selecting CONFIG_DEBUG_INFO_BTF results in the below warning from ld: ld: warning: orphan section `.BTF' from `.btf.vmlinux.bin.o' being placed in section `.BTF' Include .BTF section in vmlinux explicitly to

[RFC PATCH v1] powerpc/XIVE: SVM: share the event-queue page with the Hypervisor.

XIVE interrupt controller maintains a Event-Queue(EQ) page. This page is used to communicate events with the Hypervisor/Qemu. In Secure-VM, unless a page is shared with the Hypervisor, the Hypervisor will not be able to read/write to that page. Explicitly share the EQ page with the Hypervisor,

Re: [PATCH 3/3] mm/page_alloc: Keep memoryless cpuless node 0 offline

On Wed, 11 Mar 2020, Srikar Dronamraju wrote: > Currently Linux kernel with CONFIG_NUMA on a system with multiple > possible nodes, marks node 0 as online at boot. However in practice, > there are systems which have node 0 as memoryless and cpuless. Would it not be better and simpler to require