Re: [PATCH v6 0/7] perf report: Show branch type

Hi Arnaldo, Could this series be merged? It's more than 2 months since the last time Jiri Olsa gave the ack. Thanks Jin Yao On 6/26/2017 2:24 PM, Jin, Yao wrote: Hi maintainers, Is this patch series OK or anything I should update? Thanks Jin Yao On 6/2/2017 4:02 PM, Jin, Yao wrote:

Re: [PATCH RFC 21/26] powerpc: Remove spin_unlock_wait() arch-specific definitions

On Sun, Jul 02, 2017 at 11:58:07AM +0800, Boqun Feng wrote: > On Thu, Jun 29, 2017 at 05:01:29PM -0700, Paul E. McKenney wrote: > > There is no agreed-upon definition of spin_unlock_wait()'s semantics, > > and it appears that all callers could do just as well with a lock/unlock > > pair. This

Re: [PATCH] ptrace: Add compat PTRACE_{G,S}ETSIGMASK handlers

On Thu, Jun 29, 2017 at 05:26:37PM +0100, James Morse wrote: > compat_ptrace_request() lacks handlers for PTRACE_{G,S}ETSIGMASK, > instead using those in ptrace_request(). The compat variant should > read a compat_sigset_t from userspace instead of ptrace_request()s > sigset_t. > > While

[RFC v5 38/38] Documentation: PowerPC specific updates to memory protection keys

Add documentation updates that capture PowerPC specific changes. Signed-off-by: Ram Pai --- Documentation/vm/protection-keys.txt | 85 ++ 1 files changed, 65 insertions(+), 20 deletions(-) diff --git a/Documentation/vm/protection-keys.txt

[RFC v5 37/38] Documentation: Move protecton key documentation to arch neutral directory

Since PowerPC and Intel both support memory protection keys, moving the documenation to arch-neutral directory. Signed-off-by: Ram Pai --- Documentation/vm/protection-keys.txt | 85 + Documentation/x86/protection-keys.txt | 85

[RFC v5 36/38] selftest: PowerPC specific test updates to memory protection keys

Abstracted out the arch specific code into the header file, and added powerpc specific changes. a) added 4k-backed hpte, memory allocator, powerpc specific. b) added three test case where the key is associated after the page is accessed/allocated/mapped. c) cleaned up the code to make

[RFC v5 35/38] selftest: Move protecton key selftest to arch neutral directory

Signed-off-by: Ram Pai --- tools/testing/selftests/vm/Makefile |1 + tools/testing/selftests/vm/pkey-helpers.h | 219 tools/testing/selftests/vm/protection_keys.c | 1395 + tools/testing/selftests/x86/Makefile |2

[RFC v5 34/38] procfs: display the protection-key number associated with a vma

Display the pkey number associated with the vma in smaps of a task. The key will be seen as below: ProtectionKey: 0 Signed-off-by: Ram Pai --- arch/powerpc/kernel/setup_64.c |8 1 files changed, 8 insertions(+), 0 deletions(-) diff --git

[RFC v5 33/38] powerpc: Deliver SEGV signal on pkey violation

The value of the AMR register at the time of exception is made available in gp_regs[PT_AMR] of the siginfo. The value of the pkey, whose protection got violated, is made available in si_pkey field of the siginfo structure. Signed-off-by: Ram Pai ---

[RFC v5 32/38] powerpc: capture the violated protection key on fault

Capture the protection key that got violated in paca. This value will be used by used to inform the signal handler. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/paca.h |1 + arch/powerpc/kernel/asm-offsets.c |1 + arch/powerpc/mm/fault.c |3

[RFC v5 31/38] powerpc: introduce get_pte_pkey() helper

get_pte_pkey() helper returns the pkey associated with a address corresponding to a given mm_struct. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/book3s/64/mmu-hash.h |5 arch/powerpc/mm/hash_utils_64.c | 28 + 2 files

[RFC v5 30/38] powerpc: capture AMR register content on pkey violation

capture AMR register contents, and save it in paca whenever a pkey violation is detected. This value will be needed to deliver pkey-violation signal to the task. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/paca.h |3 +++ arch/powerpc/kernel/asm-offsets.c |

[RFC v5 29/38] powerpc: Handle exceptions caused by pkey violation

Handle Data and Instruction exceptions caused by memory protection-key. The CPU will detect the key fault if the HPTE is already programmed with the key. However if the HPTE is not hashed, a key fault will not be detected by the hardware. The software will detect pkey violation in such a

[RFC v5 28/38] powerpc: implementation for arch_vma_access_permitted()

This patch provides the implementation for arch_vma_access_permitted(). Returns true if the requested access is allowed by pkey associated with the vma. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/mmu_context.h |5 arch/powerpc/mm/pkeys.c|

[RFC v5 27/38] powerpc: Macro the mask used for checking DSI exception

Replace the magic number used to check for DSI exception with a meaningful value. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/reg.h |7 ++- arch/powerpc/kernel/exceptions-64s.S |2 +- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git

[RFC v5 26/38] powerpc: check key protection for user page access

Make sure that the kernel does not access user pages without checking their key-protection. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/book3s/64/pgtable.h | 14 ++ 1 files changed, 14 insertions(+), 0 deletions(-) diff --git

[RFC v5 25/38] powerpc: helper to validate key-access permissions of a pte

helper function that checks if the read/write/execute is allowed on the pte. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/book3s/64/pgtable.h |2 + arch/powerpc/include/asm/pkeys.h |9 +++ arch/powerpc/mm/pkeys.c | 31

[RFC v5 24/38] powerpc: Program HPTE key protection bits

Map the PTE protection key bits to the HPTE key protection bits, while creating HPTE entries. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/book3s/64/mmu-hash.h |5 + arch/powerpc/include/asm/pkeys.h |9 +

[RFC v5 23/38] powerpc: sys_pkey_mprotect() system call

Patch provides the ability for a process to associate a pkey with a address range. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/systbl.h |1 + arch/powerpc/include/asm/unistd.h |4 +--- arch/powerpc/include/uapi/asm/unistd.h |1 + 3 files

[RFC v5 22/38] powerpc: map vma key-protection bits to pte key bits.

map the pkey bits in the pte from the key protection bits of the vma. The pte bits used for pkey are 3,4,5,6 and 57. The first four bits are the same four bits that were freed up initially in this patch series. remember? :-) Without those four bits this patch would'nt be possible.

[RFC v5 21/38] powerpc: implementation for arch_override_mprotect_pkey()

arch independent code calls arch_override_mprotect_pkey() to return a pkey that best matches the requested protection. This patch provides the implementation. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/pkeys.h | 10 ++- arch/powerpc/mm/pkeys.c |

[RFC v5 20/38] powerpc: ability to associate pkey to a vma

arch-independent code expects the arch to map a pkey into the vma's protection bit setting. The patch provides that ability. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/mman.h |8 +++- arch/powerpc/include/asm/pkeys.h | 14 -- 2 files

[RFC v5 19/38] powerpc: introduce execute-only pkey

This patch provides the implementation of execute-only pkey. The architecture-independent expects the ability to create and manage a special key which has execute-only permission. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/book3s/64/mmu.h |1 +

[RFC v5 18/38] powerpc: store and restore the pkey state across context switches

Store and restore the AMR, IAMR and UMOR register state of the task before scheduling out and after scheduling in, respectively. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/processor.h |5 + arch/powerpc/kernel/process.c| 18 ++ 2

[RFC v5 17/38] powerpc: sys_pkey_alloc() and sys_pkey_free() system calls

Finally this patch provides the ability for a process to allocate and free a protection key. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/systbl.h |2 ++ arch/powerpc/include/asm/unistd.h |4 +--- arch/powerpc/include/uapi/asm/unistd.h |2 ++ 3

[RFC v5 16/38] powerpc: implementation for arch_set_user_pkey_access()

This patch provides the detailed implementation for a user to allocate a key and enable it in the hardware. It provides the plumbing, but it cannot be used yet till the system call is implemented. The next patch will do so. Signed-off-by: Ram Pai ---

[RFC v5 15/38] powerpc: helper function to read, write AMR, IAMR, UAMOR registers

Implements helper functions to read and write the key related registers; AMR, IAMR, UAMOR. AMR register tracks the read,write permission of a key IAMR register tracks the execute permission of a key UAMOR register enables and disables a key Signed-off-by: Ram Pai ---

[RFC v5 14/38] powerpc: initial plumbing for key management

Initial plumbing to manage all the keys supported by the hardware. Total 32 keys are supported on powerpc. However pkey 0,1 and 31 are reserved. So effectively we have 29 pkeys. This patch keeps track of reserved keys, allocated keys and keys that are currently free. Also it adds skeletal

[RFC v5 13/38] x86: disallow pkey creation with PKEY_DISABLE_EXECUTE

x86 does not support disabling execute permissions on a pkey. Signed-off-by: Ram Pai --- arch/x86/kernel/fpu/xstate.c |3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/arch/x86/kernel/fpu/xstate.c b/arch/x86/kernel/fpu/xstate.c index

[RFC v5 11/38] mm: introduce an additional vma bit for powerpc pkey

Currently there are only 4bits in the vma flags to support 16 keys on x86. powerpc supports 32 keys, which needs 5bits. This patch introduces an addition bit in the vma flags. Signed-off-by: Ram Pai --- fs/proc/task_mmu.c |6 +- include/linux/mm.h | 18

[RFC v5 12/38] mm: ability to disable execute permission on a key at creation

Currently sys_pkey_create() provides the ability to disable read and write permission on the key, at creation. powerpc has the hardware support to disable execute on a pkey as well.This patch enhances the interface to let disable execute at key creation time. x86 does not allow this.

[RFC v5 10/38] powerpc: use helper functions in flush_hash_page()

replace redundant code in flush_hash_page() with helper function pte_get_hash_gslot(). Signed-off-by: Ram Pai --- arch/powerpc/mm/hash_utils_64.c | 13 - 1 files changed, 4 insertions(+), 9 deletions(-) diff --git a/arch/powerpc/mm/hash_utils_64.c

[RFC v5 09/38] powerpc: use helper functions in __hash_page_4K() for 4K PTE

replace redundant code with helper functions pte_get_hash_gslot() and pte_set_hash_slot() Signed-off-by: Ram Pai --- arch/powerpc/mm/hash64_4k.c | 14 ++ 1 files changed, 6 insertions(+), 8 deletions(-) diff --git a/arch/powerpc/mm/hash64_4k.c

[RFC v5 08/38] powerpc: use helper functions in __hash_page_4K() for 64K PTE

replace redundant code in __hash_page_4K() with helper functions pte_get_hash_gslot() and pte_set_hash_slot() Signed-off-by: Ram Pai --- arch/powerpc/mm/hash64_64k.c | 34 +- 1 files changed, 9 insertions(+), 25 deletions(-) diff --git

[RFC v5 07/38] powerpc: use helper functions in __hash_page_huge() for 64K PTE

replace redundant code in __hash_page_huge() with helper functions pte_get_hash_gslot() and pte_set_hash_slot() Signed-off-by: Ram Pai --- arch/powerpc/mm/hugetlbpage-hash64.c | 24 1 files changed, 4 insertions(+), 20 deletions(-) diff --git

[RFC v5 06/38] powerpc: use helper functions in __hash_page_64K() for 64K PTE

replace redundant code in __hash_page_64K() with helper functions pte_get_hash_gslot() and pte_set_hash_slot() Signed-off-by: Ram Pai --- arch/powerpc/mm/hash64_64k.c | 24 1 files changed, 4 insertions(+), 20 deletions(-) diff --git

[RFC v5 05/38] powerpc: capture the PTE format changes in the dump pte report

The H_PAGE_F_SECOND,H_PAGE_F_GIX are not in the 64K main-PTE. capture these changes in the dump pte report. Signed-off-by: Ram Pai --- arch/powerpc/mm/dump_linuxpagetables.c |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git

[RFC v5 04/38] powerpc: introduce pte_get_hash_gslot() helper

Introduce pte_get_hash_gslot()() which returns the slot number of the HPTE in the global hash table. This function will come in handy as we work towards re-arranging the PTE bits in the later patches. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/book3s/64/hash.h |

[RFC v5 03/38] powerpc: introduce pte_set_hash_slot() helper

Introduce pte_set_hash_slot().It sets the (H_PAGE_F_SECOND|H_PAGE_F_GIX) bits at the appropriate location in the PTE of 4K PTE. For 64K PTE, it sets the bits in the second part of the PTE. Though the implementation for the former just needs the slot parameter, it does

[RFC v5 02/38] powerpc: Free up four 64K PTE bits in 64K backed HPTE pages

Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6 in the 64K backed HPTE pages. This along with the earlier patch will entirely free up the four bits from 64K PTE. The bit numbers are big-endian as defined in the ISA3.0 This patch does the following change to 64K PTE backed by 64K

[RFC v5 01/38] powerpc: Free up four 64K PTE bits in 4K backed HPTE pages

Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6, in the 4K backed HPTE pages.These bits continue to be used for 64K backed HPTE pages in this patch, but will be freed up in the next patch. The bit numbers are big-endian as defined in the ISA3.0 The patch does the following change to

[RFC v5 00/38] powerpc: Memory Protection Keys

Memory protection keys enable applications to protect its address space from inadvertent access or corruption from itself. The overall idea: A process allocates a key and associates it with an address range withinits address space. The process then can dynamically set

Re: [PATCH] powerpc/tm: fix live state of vs0/32 in tm_reclaim

Hi Michael, On Wed, Jul 05, 2017 at 11:02:41AM +1000, Michael Neuling wrote: > On Tue, 2017-07-04 at 16:45 -0400, Gustavo Romero wrote: > > Currently tm_reclaim() can return with a corrupted vs0 (fp0) or vs32 (v0) > > due to the fact vs0 is used to save FPSCR and vs32 is used to save VSCR. > >

Re: [RFC PATCH 1/2] powerpc/xive: guest exploitation of the XIVE interrupt controller

On 07/03/2017 05:55 AM, David Gibson wrote: > On Thu, Jun 22, 2017 at 11:29:16AM +0200, Cédric Le Goater wrote: >> This is the framework for using XIVE in a PowerVM guest. The support >> is very similar to the native one in a much simpler form. >> >> Instead of OPAL calls, a set of Hypervisors

Re: 85xx: Enable gpio power/reset driver

Hello Scott On 23/10/2016, Andy Fleming wrote: > These config changes build: > drivers/power/reset/gpio-poweroff.c > drivers/power/reset/gpio-restart.c > > Signed-off-by: Andy Fleming > --- > arch/powerpc/configs/fsl-emb-nonhw.config | 6 ++ > 1 file changed, 6

[PATCH 5/5] powernv:idle: Disable LOSE_FULL_CONTEXT states when stop-api fails.

From: "Gautham R. Shenoy" Currently, we use the opal call opal_slw_set_reg() to inform the that the Sleep-Winkle Engine (SLW) to restore the contents of some of the Hypervisor state on wakeup from deep idle states that lose full hypervisor context (characterized by the

[PATCH 0/5] powernv:idle: Cleanup idle states initialization

From: "Gautham R. Shenoy" Hi, This patch set aims at cleaning up the powernv idle initialization code mainly covering the following a) Currently there is redundant code for parsing the device-tree for idle states. We do it in two places, once during the platform

[PATCH 2/5] powernv:idle: Change return type of pnv_probe_idle_states to int

From: "Gautham R. Shenoy" In the current idle initialization code, if there are failures in pnv_probe_idle_states, then no platform idle state is enabled. However, since the error is not propagated to the top-level function pnv_init_idle_states, we continue

[PATCH 3/5] powernv:idle: Define idle init function for power8

From: "Gautham R. Shenoy" In this patch we define a new function named pnv_power8_idle_init(). We move the following code from pnv_init_idle_states() into this newly defined function. a) That patches out pnv_fastsleep_workaround_at_entry/exit when no states

[PATCH 1/5] powernv:idle: Move device-tree parsing to one place.

From: "Gautham R. Shenoy" The details of the platform idle state are exposed by the firmware to the kernel via device tree. In the current code, we parse the device tree twice : 1) During the boot up in arch/powerpc/platforms/powernv/idle.c Here, the device tree is

[PATCH 4/5] powernv:idle: Move initialization of sibling pacas to pnv_alloc_idle_core_states

From: "Gautham R. Shenoy" On POWER9 DD1, in order to get around a hardware issue, we store in every CPU thread's paca the paca pointers of all its siblings. Move this code into pnv_alloc_idle_core_states() soon after the space for saving the sibling pacas is allocated.

Re: [PATCH] powerpc/mm: Implemented default_hugepagesz verification for powerpc

Em 2017-07-05 01:31, Anshuman Khandual escreveu: On 07/04/2017 01:35 AM, Victor Aoqui wrote: Implemented default hugepage size verification (default_hugepagesz=) in order to allow allocation of defined number of pages (hugepages=) only for supported hugepage sizes. Signed-off-by: Victor Aoqui

Re: [PATCH] powerpc/mm: Implemented default_hugepagesz verification for powerpc

Em 2017-07-05 01:26, Aneesh Kumar K.V escreveu: On Tuesday 04 July 2017 01:35 AM, Victor Aoqui wrote: Implemented default hugepage size verification (default_hugepagesz=) in order to allow allocation of defined number of pages (hugepages=) only for supported hugepage sizes. Signed-off-by:

Re: [next-20170609] Oops while running CPU off-on (cpuset.c/cpuset_can_attach)

Hello, Abdul. Thanks for the debug info. Can you please see whether the following patch fixes the issue? If the problem is too difficult to reproduce to confirm the fix by seeing whether it no longer triggers, please let me know. We can instead apply a patch which triggers WARN on the failing

[PATCH 07/14] spufs: Implement show_options

Implement the show_options superblock op for spufs as part of a bid to get rid of s_options and generic_show_options() to make it easier to implement a context-based mount where the mount options can be passed individually over a file descriptor. Signed-off-by: David Howells

Re: [RFC PATCH 1/2] powerpc/xive: guest exploitation of the XIVE interrupt controller

On 07/05/2017 04:38 PM, Benjamin Herrenschmidt wrote: > On Wed, 2017-07-05 at 21:07 +1000, David Gibson wrote: >> I don't know if it helps, but we do have the ability to trigger a full >> system reset from CAS, so possibly we can do the XICS/XIVE >> instantiation in the reset path. >> >> I don't

Re: [RFC PATCH 1/2] powerpc/xive: guest exploitation of the XIVE interrupt controller

On Wed, 2017-07-05 at 21:07 +1000, David Gibson wrote: > I don't know if it helps, but we do have the ability to trigger a full > system reset from CAS, so possibly we can do the XICS/XIVE > instantiation in the reset path. > > I don't think we use that CAS reset ability yet - we just adjust the

Re: [PATCH v2 6/6] ima: Support module-style appended signatures for appraisal

On Tue, 2017-07-04 at 23:22 -0300, Thiago Jung Bauermann wrote: > Mimi Zohar writes: > > > On Wed, 2017-06-21 at 14:45 -0300, Thiago Jung Bauermann wrote: > >> Mimi Zohar writes: > >> > On Wed, 2017-06-07 at 22:49 -0300, Thiago Jung Bauermann

Re: [RFC PATCH 1/2] powerpc/xive: guest exploitation of the XIVE interrupt controller

On Mon, Jul 03, 2017 at 09:11:18AM +0200, Cédric Le Goater wrote: > On 07/03/2017 06:19 AM, Benjamin Herrenschmidt wrote: > > On Mon, 2017-07-03 at 13:55 +1000, David Gibson wrote: > >>> Calls that still need to be addressed : > >>> > >>> H_INT_SET_OS_REPORTING_LINE > >>>

[PATCH 3/3] powerpc/strict_kernel_rwx: Don't depend on !RELOCATABLE

The concerns with extra permissions and overlap have been address, remove the dependency on !RELOCTABLE Signed-off-by: Balbir Singh --- arch/powerpc/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig

[PATCH 2/3] powerpc/mm/hash: WARN if relocation is enabled and CONFIG_STRICT_KERNEL_RWX

For radix we split the mapping into smaller page sizes (at the cost of additional TLB overhead), but for hash its best to print a warning. In the case of hash and no-relocation, the kernel should be well aligned to provide the least overhead with the current linear mapping size (16M)

[PATCH 1/3] powerpc/mm/radix: Fix relocatable radix mappings for STRICT_RWX

The mappings now do perfect kernel pte mappings even when the kernel is relocated. This patch refactors create_physical_mapping() and mark_rodata_ro(). create_physical_mapping() is now largely done with a helper called __create_physical_mapping(), which is defined differently for when

[PATCH 0/3] Have CONFIG_STRICT_KERNEL_RWX work with CONFIG_RELOCATABLE

These patches make CONFIG_STRICT_KERNEL_RWX work with CONFIG_RELOCATABLE The first patch splits up the radix linear mapping nicely on relocation to support granular read-only and execution bits. The second patch warns if relocation is actually done (PHYSICAL_START > MEMORY_START), we do best

Re: [RFC PATCH] powerpc/powernv: report error messages from opal

Oliver O'Halloran writes: > Recent versions of skiboot will raise an OPAL event (read: interrupt) > when firmware writes an error message to its internal console. In > conjunction they provide an OPAL call that the kernel can use to extract > these messages from the OPAL log to