[PATCH v4 5/7] ocxl: Expose the thread_id needed for wait on POWER9

From: Alastair D'Silva In order to successfully issue as_notify, an AFU needs to know the TID to notify, which in turn means that this information should be available in userspace so it can be communicated to the AFU. Signed-off-by: Alastair D'Silva

[PATCH v4 7/7] ocxl: Document new OCXL IOCTLs

From: Alastair D'Silva Signed-off-by: Alastair D'Silva --- Documentation/accelerators/ocxl.rst | 11 +++ 1 file changed, 11 insertions(+) diff --git a/Documentation/accelerators/ocxl.rst b/Documentation/accelerators/ocxl.rst index

[PATCH v4 3/7] powerpc: use task_pid_nr() for TID allocation

From: Alastair D'Silva The current implementation of TID allocation, using a global IDR, may result in an errant process starving the system of available TIDs. Instead, use task_pid_nr(), as mentioned by the original author. The scenario described which prevented it's use

[PATCH v4 4/7] ocxl: Rename pnv_ocxl_spa_remove_pe to clarify it's action

From: Alastair D'Silva The function removes the process element from NPU cache. Signed-off-by: Alastair D'Silva --- arch/powerpc/include/asm/pnv-ocxl.h | 2 +- arch/powerpc/platforms/powernv/ocxl.c | 4 ++-- drivers/misc/ocxl/link.c |

[PATCH v4 2/7] powerpc: Use TIDR CPU feature to control TIDR allocation

From: Alastair D'Silva Switch the use of TIDR on it's CPU feature, rather than assuming it is available based on architecture. Signed-off-by: Alastair D'Silva --- arch/powerpc/kernel/process.c | 6 +++--- 1 file changed, 3 insertions(+), 3

[PATCH v4 6/7] ocxl: Add an IOCTL so userspace knows what OCXL features are available

From: Alastair D'Silva In order for a userspace AFU driver to call the POWER9 specific OCXL_IOCTL_ENABLE_P9_WAIT, it needs to verify that it can actually make that call. Signed-off-by: Alastair D'Silva --- drivers/misc/ocxl/file.c | 25

[PATCH v4 1/7] powerpc: Add TIDR CPU feature for POWER9

From: Alastair D'Silva This patch adds a CPU feature bit to show whether the CPU has the TIDR register available, enabling as_notify/wait in userspace. Signed-off-by: Alastair D'Silva --- arch/powerpc/include/asm/cputable.h | 3 ++-

[PATCH v4 0/7] ocxl: Implement Power9 as_notify/wait for OpenCAPI

From: Alastair D'Silva The Power 9 as_notify/wait feature provides a lower latency way to signal a thread that work is complete. This series enables the use of this feature from OpenCAPI adapters, as well as addressing a potential starvation issue when allocating thread

[PATCH v2 5/9] powerpc/mm/radix: implement LPID based TLB flushes to be used by KVM

Implement a local TLB flush for invalidating an LPID with variants for process or partition scope. And a global TLB flush for invalidating a partition scoped page of an LPID. These will be used by KVM in subsequent patches. Signed-off-by: Nicholas Piggin ---

Re: [PATCH 8/8] mm/pkeys, x86, powerpc: Display pkey in smaps if arch supports pkeys

Dave Hansen writes: > On 05/08/2018 07:59 AM, Michael Ellerman wrote: >> Currently the architecture specific code is expected to display the >> protection keys in smap for a given vma. This can lead to redundant >> code and possibly to divergent formats in which the key

Re: [PATCH 5/8] x86/pkeys: Move vma_pkey() into asm/pkeys.h

Dave Hansen writes: > On 05/08/2018 07:59 AM, Michael Ellerman wrote: >> Move the last remaining pkey helper, vma_pkey() into asm/pkeys.h > > Fine with me, as long as it compiles. :) Yeah fair point :) It survived the kbuild robot, so fingers crossed. I'll let it sit in

Re: [PATCH v3] ppc64le livepatch: implement reliable stacktrace for newer consistency models

Josh Poimboeuf writes: > On Tue, May 08, 2018 at 10:38:32AM +0200, Torsten Duwe wrote: >> On Mon, 7 May 2018 10:42:08 -0500 >> Josh Poimboeuf wrote: >> >> > The subject doesn't actively describe what the patch does, maybe >> > change it to something

[PATCH v3 5/7] ocxl: Expose the thread_id needed for wait on POWER9

From: Alastair D'Silva In order to successfully issue as_notify, an AFU needs to know the TID to notify, which in turn means that this information should be available in userspace so it can be communicated to the AFU. Signed-off-by: Alastair D'Silva

[PATCH v3 6/7] ocxl: Add an IOCTL so userspace knows what OCXL features are available

From: Alastair D'Silva In order for a userspace AFU driver to call the POWER9 specific OCXL_IOCTL_ENABLE_P9_WAIT, it needs to verify that it can actually make that call. Signed-off-by: Alastair D'Silva --- drivers/misc/ocxl/file.c | 25

[PATCH v3 7/7] ocxl: Document new OCXL IOCTLs

From: Alastair D'Silva Signed-off-by: Alastair D'Silva --- Documentation/accelerators/ocxl.rst | 11 +++ 1 file changed, 11 insertions(+) diff --git a/Documentation/accelerators/ocxl.rst b/Documentation/accelerators/ocxl.rst index

[PATCH v3 3/7] powerpc: use task_pid_nr() for TID allocation

From: Alastair D'Silva The current implementation of TID allocation, using a global IDR, may result in an errant process starving the system of available TIDs. Instead, use task_pid_nr(), as mentioned by the original author. The scenario described which prevented it's use

[PATCH v3 0/7] ocxl: Implement Power9 as_notify/wait for OpenCAPI

From: Alastair D'Silva The Power 9 as_notify/wait feature provides a lower latency way to signal a thread that work is complete. This series enables the use of this feature from OpenCAPI adapters, as well as addressing a potential starvation issue when allocating thread

[PATCH v3 4/7] ocxl: Rename pnv_ocxl_spa_remove_pe to clarify it's action

From: Alastair D'Silva The function removes the process element from NPU cache. Signed-off-by: Alastair D'Silva --- arch/powerpc/include/asm/pnv-ocxl.h | 2 +- arch/powerpc/platforms/powernv/ocxl.c | 4 ++-- drivers/misc/ocxl/link.c |

[PATCH v3 2/7] powerpc: Use TIDR CPU feature to control TIDR allocation

From: Alastair D'Silva Switch the use of TIDR on it's CPU feature, rather than assuming it is available based on architecture. Signed-off-by: Alastair D'Silva --- arch/powerpc/kernel/process.c | 6 +++--- 1 file changed, 3 insertions(+), 3

[PATCH v3 1/7] powerpc: Add TIDR CPU feature for POWER9

From: Alastair D'Silva This patch adds a CPU feature bit to show whether the CPU has the TIDR register available, enabling as_notify/wait in userspace. Signed-off-by: Alastair D'Silva --- arch/powerpc/include/asm/cputable.h | 3 ++-

Re: [PATCH v3] ppc64le livepatch: implement reliable stacktrace for newer consistency models

On Tue, May 08, 2018 at 10:38:32AM +0200, Torsten Duwe wrote: > On Mon, 7 May 2018 10:42:08 -0500 > Josh Poimboeuf wrote: > > > The subject doesn't actively describe what the patch does, maybe > > change it to something like: > > > > powerpc: Add support for

Re: [PATCH v3] powerpc, pkey: make protection key 0 less special

On Tue, May 08, 2018 at 07:03:36PM +0200, Michal Suchánek wrote: > > How is the application denied setting the permissions on key 0 if it > can program the register directly? There is a UAMOR register. The userspace can change the permissions of a given key; by modifying the bits in AMOR

Re: [PATCH v3] powerpc, pkey: make protection key 0 less special

On Tue, 8 May 2018 09:38:01 -0700 Ram Pai wrote: > On Mon, May 07, 2018 at 01:21:49PM +0200, Michal Suchánek wrote: > > On Sun, 6 May 2018 13:10:43 -0700 > > Ram Pai wrote: > > > > > On Sat, May 05, 2018 at 02:39:56PM +0200, Michal Suchánek wrote:

Re: [PATCH 8/8] mm/pkeys, x86, powerpc: Display pkey in smaps if arch supports pkeys

On 05/08/2018 07:59 AM, Michael Ellerman wrote: > Currently the architecture specific code is expected to display the > protection keys in smap for a given vma. This can lead to redundant > code and possibly to divergent formats in which the key gets > displayed. > > This patch changes the

Re: [PATCH 5/8] x86/pkeys: Move vma_pkey() into asm/pkeys.h

On 05/08/2018 07:59 AM, Michael Ellerman wrote: > Move the last remaining pkey helper, vma_pkey() into asm/pkeys.h Fine with me, as long as it compiles. :) Reviewed-by: Dave Hansen

Re: [PATCH 4/8] mm/pkeys, powerpc, x86: Provide an empty vma_pkey() in linux/pkeys.h

On 05/08/2018 07:59 AM, Michael Ellerman wrote: > Consolidate the pkey handling by providing a common empty definition > of vma_pkey() in pkeys.h when CONFIG_ARCH_HAS_PKEYS=n. > > This also removes another entanglement of pkeys.h and > asm/mmu_context.h. Looks fine to me. Thanks for

Re: [PATCH v3] powerpc, pkey: make protection key 0 less special

On Mon, May 07, 2018 at 01:21:49PM +0200, Michal Suchánek wrote: > On Sun, 6 May 2018 13:10:43 -0700 > Ram Pai wrote: > > > On Sat, May 05, 2018 at 02:39:56PM +0200, Michal Suchánek wrote: > > > On Fri, 4 May 2018 14:45:07 -0700 > > > Ram Pai wrote: > >

Re: [PATCH 4/8] mm/pkeys, powerpc, x86: Provide an empty vma_pkey() in linux/pkeys.h

On Wed, May 09, 2018 at 12:59:44AM +1000, Michael Ellerman wrote: > Consolidate the pkey handling by providing a common empty definition > of vma_pkey() in pkeys.h when CONFIG_ARCH_HAS_PKEYS=n. > > This also removes another entanglement of pkeys.h and > asm/mmu_context.h. > Reviewed-by: Ram Pai

Re: [PATCH 2/8] mm, powerpc, x86: introduce an additional vma bit for powerpc pkey

On Wed, May 09, 2018 at 12:59:42AM +1000, Michael Ellerman wrote: > From: Ram Pai > > Currently only 4bits are allocated in the vma flags to hold 16 > keys. This is sufficient for x86. PowerPC supports 32 keys, > which needs 5bits. This patch allocates an additional bit.

[PATCH 8/8] mm/pkeys, x86, powerpc: Display pkey in smaps if arch supports pkeys

From: Ram Pai Currently the architecture specific code is expected to display the protection keys in smap for a given vma. This can lead to redundant code and possibly to divergent formats in which the key gets displayed. This patch changes the implementation. It displays

[PATCH 7/8] mm/pkeys: Add an empty arch_pkeys_enabled()

Add an empty arch_pkeys_enabled() in linux/pkeys.h for the CONFIG_ARCH_HAS_PKEYS=n case. Split out of a patch by Ram Pai . Signed-off-by: Michael Ellerman --- include/linux/pkeys.h | 5 + 1 file changed, 5 insertions(+) diff --git

[PATCH 6/8] x86/pkeys: Add arch_pkeys_enabled()

This will be used in future patches to check for arch support for pkeys in generic code. Signed-off-by: Michael Ellerman --- arch/x86/include/asm/pkeys.h | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/x86/include/asm/pkeys.h b/arch/x86/include/asm/pkeys.h

[PATCH 5/8] x86/pkeys: Move vma_pkey() into asm/pkeys.h

Move the last remaining pkey helper, vma_pkey() into asm/pkeys.h Signed-off-by: Michael Ellerman --- arch/x86/include/asm/mmu_context.h | 10 -- arch/x86/include/asm/pkeys.h | 8 include/linux/pkeys.h | 2 +- 3 files changed, 9

[PATCH 4/8] mm/pkeys, powerpc, x86: Provide an empty vma_pkey() in linux/pkeys.h

Consolidate the pkey handling by providing a common empty definition of vma_pkey() in pkeys.h when CONFIG_ARCH_HAS_PKEYS=n. This also removes another entanglement of pkeys.h and asm/mmu_context.h. Signed-off-by: Michael Ellerman --- arch/powerpc/include/asm/mmu_context.h |

[PATCH 3/8] mm/pkeys: Remove include of asm/mmu_context.h from pkeys.h

While trying to unify the pkey handling in show_smap() between x86 and powerpc we stumbled across various build failures due to the order of includes between the two arches. Part of the problem is that linux/pkeys.h includes asm/mmu_context.h, and the relationship between asm/mmu_context.h and

[PATCH 2/8] mm, powerpc, x86: introduce an additional vma bit for powerpc pkey

From: Ram Pai Currently only 4bits are allocated in the vma flags to hold 16 keys. This is sufficient for x86. PowerPC supports 32 keys, which needs 5bits. This patch allocates an additional bit. Reviewed-by: Ingo Molnar Acked-by: Balbir Singh

[PATCH 1/8] mm, powerpc, x86: define VM_PKEY_BITx bits if CONFIG_ARCH_HAS_PKEYS is enabled

From: Ram Pai VM_PKEY_BITx are defined only if CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS is enabled. Powerpc also needs these bits. Hence lets define the VM_PKEY_BITx bits for any architecture that enables CONFIG_ARCH_HAS_PKEYS. Reviewed-by: Dave Hansen

[PATCH 0/8] mm, x86, powerpc: Consolidate pkey code

This is a rework of Ram's series, which broke the build on both arches at various points due to the differing header dependencies. The actual pkey changes are basically the same, this just has some rework to get the headers cleaned up a bit beforehand. If no one objects I'll ask Stephen to put

Re: powerpc/fadump: Unregister fadump on kexec down path.

On Fri, 2018-04-27 at 06:23:18 UTC, Mahesh J Salgaonkar wrote: > From: Mahesh Salgaonkar > > Unregister fadump on kexec down path otherwise the fadump registration in > new kexec-ed kernel complains that fadump is already registered. This > makes new kernel to continue

Re: tracing: Remove PPC32 wart from config TRACING_SUPPORT

On Wed, 2018-05-02 at 11:29:48 UTC, Michael Ellerman wrote: > config TRACING_SUPPORT has an exception for PPC32, because PPC32 > didn't have irqflags tracing support. > > But that hasn't been true since commit 5d38902c4838 ("powerpc: Add > irqtrace support for 32-bit powerpc") (Jun 2009). > > So

Re: [resend] Revert "powerpc/powernv: Increase memory block size to 1GB on radix"

On Tue, 2018-05-01 at 02:57:25 UTC, Balbir Singh wrote: > This commit was a stop-gap to prevent crashes on hotunplug, caused by > the mismatch between the 1G mappings used for the linear mapping and the > memory block size. Those issues are now resolved because we split the > linear mapping at

Re: [1/3] powerpc/nohash: remove hash related code from nohash headers.

On Tue, 2018-04-24 at 16:31:28 UTC, Christophe Leroy wrote: > When nohash and book3s header were split, some hash related stuff > remained in the nohash header. This patch removes them. > > Signed-off-by: Christophe Leroy Series applied to powerpc next, thanks.

Re: [v5, 01/10] powerpc64/ftrace: Add a field in paca to disable ftrace in unsafe code paths

On Thu, 2018-04-19 at 07:04:00 UTC, "Naveen N. Rao" wrote: > We have some C code that we call into from real mode where we cannot > take any exceptions. Though the C functions themselves are mostly safe, > if these functions are traced, there is a possibility that we may take > an exception. For

Re: [v2, 1/2] powerpc/fadump: exclude memory holes while reserving memory in second kernel

On Tue, 2018-04-10 at 13:41:16 UTC, Hari Bathini wrote: > From: Mahesh Salgaonkar > > The second kernel, during early boot after the crash, reserves rest of > the memory above boot memory size to make sure it does not touch any of the > dump memory area. It uses

Re: powerpc: Only support DYNAMIC_FTRACE not static

On Tue, 2018-03-27 at 04:29:06 UTC, Michael Ellerman wrote: > We've had dynamic ftrace support for over 9 years since Steve first > wrote it, all the distros use dynamic, and static is basically > untested these days, so drop support for static ftrace. > > Signed-off-by: Michael Ellerman

Re: [PATCH-next] powerpc: remove retired sbc834x support

On Mon, 2017-12-11 at 03:29:13 UTC, Paul Gortmaker wrote: > I no longer have a functional version of this board for even the most > basic sanity boot testing, and they have not been available for purchase > for quite some years now. > > There is no point in adding a burden to testing coverage

Re: [PATCH 2/2] powerpc/ptrace: Disable array-bounds warning with gcc8

Khem Raj writes: > This masks the new gcc8 warning > > regset.h:270:4: error: 'memcpy' offset [-527, -529] is out > of the bounds [0, 16] of object 'vrsave' with type 'union ' Why would we want to mask the warning rather than fix it? cheers > Signed-off-by: Khem Raj

Re: [PATCH v13 0/3] mm, x86, powerpc: Enhancements to Memory Protection Keys.

Ram Pai writes: > This patch series provides arch-neutral enhancements to > enable memory-keys on new architecutes, and the corresponding > changes in x86 and powerpc specific code to support that. > > a) Provides ability to support upto 32 keys. PowerPC > can

Re: seccomp_bpf.c:2880:global.get_metadata:Expected 0 (0) == seccomp(1, 2, ) (4294967295)

Mathieu Malaterre writes: > Hi there, > > Quick question (I have not investigate root cause): is support for > seccomp complete on ppc32 ? Doesn't look like it does it :) > $ make KBUILD_OUTPUT=/tmp/kselftest TARGETS=seccomp kselftest > ... >

Re: [PATCH] pkeys: Introduce PKEY_ALLOC_SIGNALINHERIT and change signal semantics

On 05/08/2018 04:49 AM, Andy Lutomirski wrote: On Mon, May 7, 2018 at 2:48 AM Florian Weimer wrote: On 05/03/2018 06:05 AM, Andy Lutomirski wrote: On Wed, May 2, 2018 at 7:11 PM Ram Pai wrote: On Wed, May 02, 2018 at 09:23:49PM +, Andy

Re: [PATCH] powerpc/pseries: hcall_exit tracepoint retval should be signed

Hi Michael, > The hcall_exit() tracepoint has retval defined as unsigned long. That > leads to humours results like: > > bash-3686 [009] d..2 854.134094: hcall_entry: opcode=24 > bash-3686 [009] d..2 854.134095: hcall_exit: opcode=24 > retval=18446744073709551609 > > It's normal for

Re: [PATCH v10 02/25] x86/mm: define ARCH_SUPPORTS_SPECULATIVE_PAGE_FAULT

Hi Laurent, Laurent Dufour writes: > Set ARCH_SUPPORTS_SPECULATIVE_PAGE_FAULT which turns on the > Speculative Page Fault handler when building for 64bit. > > Cc: Thomas Gleixner > Signed-off-by: Laurent Dufour > ---

Re: [PATCH v10 12/25] mm: cache some VMA fields in the vm_fault structure

On Fri, May 04, 2018 at 11:10:54AM +0200, Laurent Dufour wrote: > On 03/05/2018 17:42, Minchan Kim wrote: > > On Thu, May 03, 2018 at 02:25:18PM +0200, Laurent Dufour wrote: > >> On 23/04/2018 09:42, Minchan Kim wrote: > >>> On Tue, Apr 17, 2018 at 04:33:18PM +0200, Laurent Dufour wrote: >

[PATCH v2 1/4] powerpc/64/kexec: fix race in kexec when XIVE is shutdown

The kexec_state KEXEC_STATE_IRQS_OFF barrier is reached by all secondary CPUs before the kexec_cpu_down() operation is called on secondaries. This can raise conflicts and provoque errors in the XIVE hcalls when XIVE is shutdown with H_INT_RESET on the primary CPU. To synchronize the

[PATCH v2 3/4] powerpc/xive: shutdown XIVE when kexec or kdump is performed

The hcall H_INT_RESET should be called to make sure XIVE is fully reseted. Signed-off-by: Cédric Le Goater --- arch/powerpc/platforms/pseries/kexec.c | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/arch/powerpc/platforms/pseries/kexec.c

Re: [PATCH 09/17] powerpc: make __ioremap_caller() common to PPC32 and PPC64

Christophe Leroy writes: > Signed-off-by: Christophe Leroy > --- > arch/powerpc/include/asm/book3s/64/pgtable.h | 1 + > arch/powerpc/mm/ioremap.c| 126 > +++ > 2 files changed, 34 insertions(+),

Re: [PATCH v3] ppc64le livepatch: implement reliable stacktrace for newer consistency models

On Mon, 7 May 2018 10:42:08 -0500 Josh Poimboeuf wrote: > The subject doesn't actively describe what the patch does, maybe > change it to something like: > > powerpc: Add support for HAVE_RELIABLE_STACKTRACE > > or maybe > > powerpc: Add support for livepatch

Re: [PATCH 02/17] powerpc/nohash: remove _PAGE_BUSY

Christophe Leroy writes: > _PAGE_BUSY is always 0, remove it > Reviewed-by: Aneesh Kumar K.V > Signed-off-by: Christophe Leroy > --- > arch/powerpc/include/asm/nohash/64/pgtable.h | 10 +++--- >

Re: [PATCH 01/17] powerpc/nohash: remove hash related code from nohash headers.

Christophe Leroy writes: > When nohash and book3s header were split, some hash related stuff > remained in the nohash header. This patch removes them. > Thanks for doing this. This was on the TODO list for a long time. When we did the split for book3s, I mostly copied

[PATCH v2 4/4] powerpc/xive: prepare all hcalls to support long busy delays

This is not the case for the moment, but future releases of pHyp might need to introduce some synchronisation routines under the hood which would make the XIVE hcalls longer to complete. As this was done for H_INT_RESET, let's wrap the other hcalls in a loop catching the H_LONG_BUSY_* codes.

[PATCH v2 2/4] powerpc/xive: fix hcall H_INT_RESET to support long busy delays

The hcall H_INT_RESET can take some time to complete and in such cases it returns H_LONG_BUSY_* codes requiring the machine to sleep for a while before retrying. Signed-off-by: Cédric Le Goater --- Changes since v2: - replaced msleep() by mdelay() as some calling path are

[PATCH v2 0/4] powerpc/xive: add support for H_INT_RESET

Hello, H_INT_RESET performs a reset of the Hypervisor internal interrupt structures, removing all settings done with H_INT_SET_SOURCE_CONFIG and H_INT_SET_QUEUE_CONFIG. This is most important for kdump and kexec to be able to restart in a clean state. First patch closes a window in the kexec