[RFC PATCH 2/2] powerpc/pmem: Disable synchronous fault by default.

2020-05-28 Thread Aneesh Kumar K.V
This adds a kernel config option that controls whether MAP_SYNC is enabled by default. With POWER10, architecture is adding new pmem flush and sync instructions. The kernel should prevent the usage of MAP_SYNC if applications are not using the new instructions on newer hardware. This config

[RFC PATCH 1/2] libnvdimm: Add prctl control for disabling synchronous fault support.

2020-05-28 Thread Aneesh Kumar K.V
With POWER10, architecture is adding new pmem flush and sync instructions. The kernel should prevent the usage of MAP_SYNC if applications are not using the new instructions on newer hardware. This patch adds a prctl option MAP_SYNC_ENABLE that can be used to enable the usage of MAP_SYNC. The

[PATCH v4 8/8] powerpc/pmem: Initialize pmem device on newer hardware

2020-05-28 Thread Aneesh Kumar K.V
With kernel now supporting new pmem flush/sync instructions, we can now enable the kernel to initialize the device. On P10 these devices would appear with a new compatible string. For PAPR device we have compatible "ibm,pmemory-v2" and for OF pmem device we have compatible

[PATCH v4 7/8] powerpc/book3s/pmem: Add WARN_ONCE to catch the wrong usage of pmem flush functions.

2020-05-28 Thread Aneesh Kumar K.V
We only support persistent memory on P8 and above. This is enforced by the firmware and further checked on virtualzied platform during platform init. Add WARN_ONCE in pmem flush routines to catch the wrong usage of these. Signed-off-by: Aneesh Kumar K.V --- arch/powerpc/include/asm/cacheflush.h

[PATCH v4 6/8] powerpc/pmem: Avoid the barrier in flush routines

2020-05-28 Thread Aneesh Kumar K.V
nvdimm expect the flush routines to just mark the cache clean. The barrier that mark the store globally visible is done in nvdimm_flush(). Update the papr_scm driver to a simplified nvdim_flush callback that do only the required barrier. Signed-off-by: Aneesh Kumar K.V ---

[PATCH v4 4/8] libnvdimm/nvdimm/flush: Allow architecture to override the flush barrier

2020-05-28 Thread Aneesh Kumar K.V
Architectures like ppc64 provide persistent memory specific barriers that will ensure that all stores for which the modifications are written to persistent storage by preceding dcbfps and dcbstps instructions have updated persistent storage before any data access or data transfer caused by

[PATCH v4 5/8] powerpc/pmem/of_pmem: Update of_pmem to use the new barrier instruction.

2020-05-28 Thread Aneesh Kumar K.V
of_pmem on POWER10 can now use phwsync instead of hwsync to ensure all previous writes are architecturally visible for the platform buffer flush. Signed-off-by: Aneesh Kumar K.V --- arch/powerpc/include/asm/cacheflush.h | 7 +++ 1 file changed, 7 insertions(+) diff --git

[PATCH v4 3/8] powerpc/pmem: Add flush routines using new pmem store and sync instruction

2020-05-28 Thread Aneesh Kumar K.V
Start using dcbstps; phwsync; sequence for flushing persistent memory range. The new instructions are implemented as a variant of dcbf and hwsync and on P8 and P9 they will be executed as those instructions. We avoid using them on older hardware. This helps to avoid difficult to debug bugs.

[PATCH v4 2/8] powerpc/pmem: Add new instructions for persistent storage and sync

2020-05-28 Thread Aneesh Kumar K.V
POWER10 introduces two new variants of dcbf instructions (dcbstps and dcbfps) that can be used to write modified locations back to persistent storage. Additionally, POWER10 also introduce phwsync and plwsync which can be used to establish order of these writes to persistent storage. This patch

[PATCH v4 0/8] Support new pmem flush and sync instructions for POWER

2020-05-28 Thread Aneesh Kumar K.V
This patch series enables the usage os new pmem flush and sync instructions on POWER architecture. POWER10 introduces two new variants of dcbf instructions (dcbstps and dcbfps) that can be used to write modified locations back to persistent storage. Additionally, POWER10 also introduce phwsync

[PATCH v4 1/8] powerpc/pmem: Restrict papr_scm to P8 and above.

2020-05-28 Thread Aneesh Kumar K.V
The PAPR based virtualized persistent memory devices are only supported on POWER9 and above. In the followup patch, the kernel will switch the persistent memory cache flush functions to use a new `dcbf` variant instruction. The new instructions even though added in ISA 3.1 works even on P8 and P9

Re: [PATCH] powerpc/xive: Enforce load-after-store ordering when StoreEOI is active

2020-05-28 Thread Michael Ellerman
On Thu, 2020-02-20 at 08:15:06 UTC, =?UTF-8?q?C=C3=A9dric=20Le=20Goater?= wrote: > When an interrupt has been handled, the OS notifies the interrupt > controller with a EOI sequence. On a POWER9 system using the XIVE > interrupt controller, this can be done with a load or a store > operation on

Re: [PATCH] powerpc/uaccess: Don't use "m<>" constraint

2020-05-28 Thread Michael Ellerman
On Thu, 2020-05-07 at 12:33:24 UTC, Michael Ellerman wrote: > The "m<>" constraint breaks compilation with GCC 4.6.x era compilers. > > The use of the constraint allows the compiler to use update-form > instructions, however in practice current compilers never generate > those forms for any of

Re: [PATCH v4 2/2] powerpc/uaccess: Implement unsafe_copy_to_user() as a simple loop

2020-05-28 Thread Michael Ellerman
On Fri, 2020-04-17 at 17:08:52 UTC, Christophe Leroy wrote: > At the time being, unsafe_copy_to_user() is based on > raw_copy_to_user() which calls __copy_tofrom_user(). > > __copy_tofrom_user() is a big optimised function to copy big amount > of data. It aligns destinations to cache line in

Re: [PATCH v4 1/2] powerpc/uaccess: Implement unsafe_put_user() using 'asm goto'

2020-05-28 Thread Michael Ellerman
On Fri, 2020-04-17 at 17:08:51 UTC, Christophe Leroy wrote: > unsafe_put_user() is designed to take benefit of 'asm goto'. > > Instead of using the standard __put_user() approach and branch > based on the returned error, use 'asm goto' and make the > exception code branch directly to the error

Re: [PATCH v3] powerpc/uaccess: evaluate macro arguments once, before user access is allowed

2020-05-28 Thread Michael Ellerman
On Tue, 2020-04-07 at 04:12:45 UTC, Nicholas Piggin wrote: > get/put_user can be called with nontrivial arguments. fs/proc/page.c > has a good example: > > if (put_user(stable_page_flags(ppage), out)) { > > stable_page_flags is quite a lot of code, including spin locks in the > page

Re: [PATCH v2 4/5] powerpc/uaccess: Implement user_read_access_begin and user_write_access_begin

2020-05-28 Thread Michael Ellerman
On Fri, 2020-04-03 at 07:20:53 UTC, Christophe Leroy wrote: > Add support for selective read or write user access with > user_read_access_begin/end and user_write_access_begin/end. > > Signed-off-by: Christophe Leroy > Reviewed-by: Kees Cook Applied to powerpc topic/uaccess-ppc, thanks.

Re: [PATCH v2 3/5] drm/i915/gem: Replace user_access_begin by user_write_access_begin

2020-05-28 Thread Michael Ellerman
On Fri, 2020-04-03 at 07:20:52 UTC, Christophe Leroy wrote: > When i915_gem_execbuffer2_ioctl() is using user_access_begin(), > that's only to perform unsafe_put_user() so use > user_write_access_begin() in order to only open write access. > > Signed-off-by: Christophe Leroy > Reviewed-by: Kees

Re: [PATCH v2 2/5] uaccess: Selectively open read or write user access

2020-05-28 Thread Michael Ellerman
On Fri, 2020-04-03 at 07:20:51 UTC, Christophe Leroy wrote: > When opening user access to only perform reads, only open read access. > When opening user access to only perform writes, only open write > access. > > Signed-off-by: Christophe Leroy > Reviewed-by: Kees Cook Applied to powerpc

Re: [PATCH v2 1/5] uaccess: Add user_read_access_begin/end and user_write_access_begin/end

2020-05-28 Thread Michael Ellerman
On Fri, 2020-04-03 at 07:20:50 UTC, Christophe Leroy wrote: > Some architectures like powerpc64 have the capability to separate > read access and write access protection. > For get_user() and copy_from_user(), powerpc64 only open read access. > For put_user() and copy_to_user(), powerpc64 only

Re: [PATCH] powerpc/nvram: Replace kmalloc with kzalloc in the error message

2020-05-28 Thread Michael Ellerman
Yi Wang writes: > From: Liao Pingfang > > Use kzalloc instead of kmalloc in the error message according to > the previous kzalloc() call. Please just remove the message instead, it's a tiny allocation that's unlikely to ever fail, and the caller will print an error anyway. cheers > diff --git

Re: powerpc/pci: [PATCH 1/1 V3] PCIE PHB reset

2020-05-28 Thread Sam Bobroff
On Tue, May 26, 2020 at 08:21:59AM -0500, wenxi...@linux.vnet.ibm.com wrote: > From: Wen Xiong > > Several device drivers hit EEH(Extended Error handling) when triggering > kdump on Pseries PowerVM. This patch implemented a reset of the PHBs > in pci general code when triggering kdump. PHB reset

Re: powerpc/pci: [PATCH 1/1 V3] PCIE PHB reset

2020-05-28 Thread Oliver O'Halloran
On Wed, May 27, 2020 at 12:48 AM wrote: > > From: Wen Xiong > > Several device drivers hit EEH(Extended Error handling) when triggering > kdump on Pseries PowerVM. This patch implemented a reset of the PHBs > in pci general code when triggering kdump. PHB reset stop all PCI > transactions from

Re: [PATCH v2] selftests: powerpc: Add test for execute-disabled pkeys

2020-05-28 Thread Michael Ellerman
Hi Sandipan, A few comments below ... Sandipan Das writes: > Apart from read and write access, memory protection keys can > also be used for restricting execute permission of pages on > powerpc. This adds a test to verify if the feature works as > expected. > > Signed-off-by: Sandipan Das >

Re: [RFC PATCH 1/4] powerpc/64s: Don't init FSCR_DSCR in __init_FSCR()

2020-05-28 Thread Alistair Popple
For what it's worth I tested this series on Mambo PowerNV and it seems to correctly enable/disable the prefix FSCR bit based on the cpu feature so feel free to add: Tested-by: Alistair Popple Mikey is going to test out pseries. - Alistair On Thursday, 28 May 2020 12:58:40 AM AEST Michael

[PATCH] powerpc/nvram: Replace kmalloc with kzalloc in the error message

2020-05-28 Thread Yi Wang
From: Liao Pingfang Use kzalloc instead of kmalloc in the error message according to the previous kzalloc() call. Signed-off-by: Liao Pingfang --- arch/powerpc/kernel/nvram_64.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/kernel/nvram_64.c

[powerpc:next-test] BUILD SUCCESS bc26d22277c297c35013700e40f276e37b991980

2020-05-28 Thread kbuild test robot
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next-test branch HEAD: bc26d22277c297c35013700e40f276e37b991980 powerpc/pseries: Update hv-24x7 information after migration Warning in current branch: kernel/events/hw_breakpoint.c:216:12: warning: no previous

Re: [PATCH] powerpc/bpf: Enable bpf_probe_read{, str}() on powerpc again

2020-05-28 Thread Michael Ellerman
Daniel Borkmann writes: > On 5/28/20 2:23 PM, Michael Ellerman wrote: >> Petr Mladek writes: >>> On Thu 2020-05-28 11:03:43, Michael Ellerman wrote: Petr Mladek writes: > The commit 0ebeea8ca8a4d1d453a ("bpf: Restrict bpf_probe_read{, str}() > only > to archs where they work")

[PATCH] powerpc: Fix misleading small cores print

2020-05-28 Thread Michael Neuling
Currently when we boot on a big core system, we get this print: [0.040500] Using small cores at SMT level This is misleading as we've actually detected big cores. This patch clears up the print to say we've detect big cores but are using small cores for scheduling. Signed-off-by: Michael

Re: [PATCH v8 1/5] powerpc: Document details on H_SCM_HEALTH hcall

2020-05-28 Thread Vaibhav Jain
Thanks for looking into this patchset Dan, Dan Williams writes: > On Tue, May 26, 2020 at 9:13 PM Vaibhav Jain wrote: >> >> Add documentation to 'papr_hcalls.rst' describing the bitmap flags >> that are returned from H_SCM_HEALTH hcall as per the PAPR-SCM >> specification. >> > > Please do a

[PATCH net] drivers/net/ibmvnic: Update VNIC protocol version reporting

2020-05-28 Thread Thomas Falcon
VNIC protocol version is reported in big-endian format, but it is not byteswapped before logging. Fix that, and remove version comparison as only one protocol version exists at this time. Signed-off-by: Thomas Falcon --- drivers/net/ethernet/ibm/ibmvnic.c | 8 +++- 1 file changed, 3

Re: [PATCH] powerpc/bpf: Enable bpf_probe_read{, str}() on powerpc again

2020-05-28 Thread Daniel Borkmann
On 5/28/20 2:23 PM, Michael Ellerman wrote: Petr Mladek writes: On Thu 2020-05-28 11:03:43, Michael Ellerman wrote: Petr Mladek writes: The commit 0ebeea8ca8a4d1d453a ("bpf: Restrict bpf_probe_read{, str}() only to archs where they work") caused that bpf_probe_read{, str}() functions were

Re: [PATCH] powerpc/64s: Fix restore of NV GPRs after facility unavailable exception

2020-05-28 Thread Michael Ellerman
On Tue, 26 May 2020 16:18:08 +1000, Michael Ellerman wrote: > Commit 702f09805222 ("powerpc/64s/exception: Remove lite interrupt > return") changed the interrupt return path to not restore non-volatile > registers by default, and explicitly restore them in paths where it is > required. > > But it

Re: [PATCH] powerpc/64s: Disable STRICT_KERNEL_RWX

2020-05-28 Thread Michael Ellerman
On Wed, 20 May 2020 23:36:05 +1000, Michael Ellerman wrote: > Several strange crashes have been eventually traced back to > STRICT_KERNEL_RWX and its interaction with code patching. > > Various paths in our ftrace, kprobes and other patching code need to > be hardened against patching failures,

Re: [PATCH] Revert "powerpc/32s: reorder Linux PTE bits to better match Hash PTE bits."

2020-05-28 Thread Michael Ellerman
On Wed, 20 May 2020 10:23:45 + (UTC), Christophe Leroy wrote: > This reverts commit 697ece78f8f749aeea40f2711389901f0974017a. > > The implementation of SWAP on powerpc requires page protection > bits to not be one of the least significant PTE bits. > > Until the SWAP implementation is

Re: [PATCH v2] powerpc/wii: Fix declaration made after definition

2020-05-28 Thread Michael Ellerman
Nathan Chancellor writes: > A 0day randconfig uncovered an error with clang, trimmed for brevity: > > arch/powerpc/platforms/embedded6xx/wii.c:195:7: error: attribute > declaration must precede definition [-Werror,-Wignored-attributes] > if (!machine_is(wii)) > ^ > > The

Re: [PATCH 2/3] powerpc/pci: unmap legacy INTx interrupts of passthrough IO adapters

2020-05-28 Thread Michael Ellerman
Cédric Le Goater writes: > On 4/29/20 9:51 AM, Cédric Le Goater wrote: >> When a passthrough IO adapter is removed from a pseries machine using >> hash MMU and the XIVE interrupt mode, the POWER hypervisor, pHyp, >> expects the guest OS to have cleared all page table entries related to >> the

Re: [PATCH v3 1/3] riscv: Move kernel mapping to vmalloc zone

2020-05-28 Thread Alex Ghiti
Hi Zong, Le 5/27/20 à 3:29 AM, Alex Ghiti a écrit : Le 5/27/20 à 2:05 AM, Zong Li a écrit : On Wed, May 27, 2020 at 1:06 AM Alex Ghiti wrote: Hi Zong, Le 5/26/20 à 5:43 AM, Zong Li a écrit : On Sun, May 24, 2020 at 4:54 PM Alexandre Ghiti wrote: This is a preparatory patch for

Re: [PATCH] powerpc/64: Remove unused generic_secondary_thread_init()

2020-05-28 Thread Michael Ellerman
Jordan Niethe writes: > On Tue, May 26, 2020 at 4:36 PM Michael Ellerman wrote: >> >> The last caller was removed in 2014 in commit fb5a515704d7 ("powerpc: >> Remove platforms/wsp and associated pieces"). >> >> Once generic_secondary_thread_init() is removed there are no longer >> any uses of

Re: [PATCH] powerpc/book3s64/kvm: Fix secondary page table walk warning during migration

2020-05-28 Thread Aneesh Kumar K.V
On 5/28/20 6:23 PM, Michael Ellerman wrote: "Aneesh Kumar K.V" writes: This patch fix the below warning reported during migration. find_kvm_secondary_pte called with kvm mmu_lock not held CPU: 23 PID: 5341 Comm: qemu-system-ppc Tainted: GW

Re: [PATCH V4 1/2] powerpc/perf: Add support for outputting extended regs in perf intr_regs

2020-05-28 Thread Nageswara R Sastry
"Linuxppc-dev" wrote on 27/05/2020 03:20:17 PM: > From: "Athira Rajeev" > To: linuxppc-dev@lists.ozlabs.org > Cc: ravi.bango...@linux.ibm.com, atraj...@linux.vnet.ibm.com, > ma...@linux.vnet.ibm.com, linux-ker...@vger.kernel.org, > a...@kernel.org, a...@linux.vnet.ibm.com, jo...@kernel.org >

Re: [PATCH V4 2/2] tools/perf: Add perf tools support for extended register capability in powerpc

2020-05-28 Thread Nageswara R Sastry
"Athira Rajeev" wrote on 27/05/2020 03:20:18 PM: > From: "Athira Rajeev" > To: linuxppc-dev@lists.ozlabs.org > Cc: linux-ker...@vger.kernel.org, ravi.bango...@linux.ibm.com, > ma...@linux.vnet.ibm.com, a...@kernel.org, a...@linux.vnet.ibm.com, > jo...@kernel.org, m...@ellerman.id.au,

Re: [PATCH] powerpc/book3s64/kvm: Fix secondary page table walk warning during migration

2020-05-28 Thread Michael Ellerman
"Aneesh Kumar K.V" writes: > This patch fix the below warning reported during migration. > > find_kvm_secondary_pte called with kvm mmu_lock not held > CPU: 23 PID: 5341 Comm: qemu-system-ppc Tainted: GW > 5.7.0-rc5-kvm-00211-g9ccf10d6d088 #432 > NIP: c00800fe848c LR:

Re: [PATCH] powerpc/bpf: Enable bpf_probe_read{, str}() on powerpc again

2020-05-28 Thread Michael Ellerman
Petr Mladek writes: > On Thu 2020-05-28 11:03:43, Michael Ellerman wrote: >> Petr Mladek writes: >> > The commit 0ebeea8ca8a4d1d453a ("bpf: Restrict bpf_probe_read{, str}() only >> > to archs where they work") caused that bpf_probe_read{, str}() functions >> > were not longer available on

[PATCH AUTOSEL 4.4 4/7] net/ethernet/freescale: rework quiesce/activate for ucc_geth

2020-05-28 Thread Sasha Levin
From: Valentin Longchamp [ Upstream commit 79dde73cf9bcf1dd317a2667f78b758e9fe139ed ] ugeth_quiesce/activate are used to halt the controller when there is a link change that requires to reconfigure the mac. The previous implementation called netif_device_detach(). This however causes the

[PATCH AUTOSEL 4.9 5/9] net/ethernet/freescale: rework quiesce/activate for ucc_geth

2020-05-28 Thread Sasha Levin
From: Valentin Longchamp [ Upstream commit 79dde73cf9bcf1dd317a2667f78b758e9fe139ed ] ugeth_quiesce/activate are used to halt the controller when there is a link change that requires to reconfigure the mac. The previous implementation called netif_device_detach(). This however causes the

[PATCH AUTOSEL 4.14 08/13] net/ethernet/freescale: rework quiesce/activate for ucc_geth

2020-05-28 Thread Sasha Levin
From: Valentin Longchamp [ Upstream commit 79dde73cf9bcf1dd317a2667f78b758e9fe139ed ] ugeth_quiesce/activate are used to halt the controller when there is a link change that requires to reconfigure the mac. The previous implementation called netif_device_detach(). This however causes the

[PATCH AUTOSEL 4.19 12/17] net/ethernet/freescale: rework quiesce/activate for ucc_geth

2020-05-28 Thread Sasha Levin
From: Valentin Longchamp [ Upstream commit 79dde73cf9bcf1dd317a2667f78b758e9fe139ed ] ugeth_quiesce/activate are used to halt the controller when there is a link change that requires to reconfigure the mac. The previous implementation called netif_device_detach(). This however causes the

[PATCH AUTOSEL 5.4 15/26] net/ethernet/freescale: rework quiesce/activate for ucc_geth

2020-05-28 Thread Sasha Levin
From: Valentin Longchamp [ Upstream commit 79dde73cf9bcf1dd317a2667f78b758e9fe139ed ] ugeth_quiesce/activate are used to halt the controller when there is a link change that requires to reconfigure the mac. The previous implementation called netif_device_detach(). This however causes the

[PATCH AUTOSEL 5.6 30/47] net/ethernet/freescale: rework quiesce/activate for ucc_geth

2020-05-28 Thread Sasha Levin
From: Valentin Longchamp [ Upstream commit 79dde73cf9bcf1dd317a2667f78b758e9fe139ed ] ugeth_quiesce/activate are used to halt the controller when there is a link change that requires to reconfigure the mac. The previous implementation called netif_device_detach(). This however causes the

[PATCH] powerpc/32: disable KASAN with pages bigger than 16k

2020-05-28 Thread Christophe Leroy
Mapping of early shadow area is implemented by using a single static page table having all entries pointing to the same early shadow page. The shadow area must therefore occupy full PGD entries. The shadow area has a size of 128Mbytes starting at 0xf800. With 4k pages, a PGD entry is 4Mbytes

Re: [PATCH] powerpc/bpf: Enable bpf_probe_read{, str}() on powerpc again

2020-05-28 Thread Petr Mladek
On Thu 2020-05-28 11:03:43, Michael Ellerman wrote: > Petr Mladek writes: > > The commit 0ebeea8ca8a4d1d453a ("bpf: Restrict bpf_probe_read{, str}() only > > to archs where they work") caused that bpf_probe_read{, str}() functions > > were not longer available on architectures where the same

Re: [RFC PATCH 1/4] powerpc/64s: Don't init FSCR_DSCR in __init_FSCR()

2020-05-28 Thread Nicholas Piggin
Excerpts from Michael Ellerman's message of May 28, 2020 12:58 am: > __init_FSCR() was added originally in commit 2468dcf641e4 ("powerpc: > Add support for context switching the TAR register") (Feb 2013), and > only set FSCR_TAR. > > At that point FSCR (Facility Status and Control Register) was

[PATCH] powerpc/book3s64/kvm: Fix secondary page table walk warning during migration

2020-05-28 Thread Aneesh Kumar K.V
This patch fix the below warning reported during migration. find_kvm_secondary_pte called with kvm mmu_lock not held CPU: 23 PID: 5341 Comm: qemu-system-ppc Tainted: GW 5.7.0-rc5-kvm-00211-g9ccf10d6d088 #432 NIP: c00800fe848c LR: c00800fe8488 CTR:

Re: [PATCH v4 09/22] powerpc/kvm/book3s: Add helper to walk partition scoped linux page table.

2020-05-28 Thread Paul Mackerras
On Thu, May 28, 2020 at 11:31:04AM +0530, Aneesh Kumar K.V wrote: > On 5/28/20 7:13 AM, Paul Mackerras wrote: > > On Tue, May 05, 2020 at 12:47:16PM +0530, Aneesh Kumar K.V wrote: > > > The locking rules for walking partition scoped table is different from > > > process > > > scoped table. Hence

[PATCH v5] KVM: PPC: clean up redundant kvm_run parameters in assembly

2020-05-28 Thread Tianjia Zhang
In the current kvm version, 'kvm_run' has been included in the 'kvm_vcpu' structure. For historical reasons, many kvm-related function parameters retain the 'kvm_run' and 'kvm_vcpu' parameters at the same time. This patch does a unified cleanup of these remaining redundant parameters.

Re: [PATCH v4 09/22] powerpc/kvm/book3s: Add helper to walk partition scoped linux page table.

2020-05-28 Thread Aneesh Kumar K.V
On 5/28/20 7:13 AM, Paul Mackerras wrote: On Tue, May 05, 2020 at 12:47:16PM +0530, Aneesh Kumar K.V wrote: The locking rules for walking partition scoped table is different from process scoped table. Hence add a helper for secondary linux page table walk and also add check whether we are