Re: [PATCH] powerpc/mm/radix: GR field got removed in ISA 3.0B

On Wed, Jun 21, 2017 at 10:50:12AM +0530, Aneesh Kumar K.V wrote: > The bit position is now marked reserved. Hence don't set the bit to 1. > > Signed-off-by: Aneesh Kumar K.V > --- > arch/powerpc/include/asm/book3s/64/mmu.h | 1 - > arch/powerpc/kvm/book3s_hv.c

Re: [PATCH V4 2/2] powerpc/powernv : Add support for OPAL-OCC command/response interface

Hi Cyril, On 06/22/2017 06:28 AM, Cyril Bur wrote: > On Wed, 2017-06-21 at 13:36 +0530, Shilpasri G Bhat wrote: >> In P9, OCC (On-Chip-Controller) supports shared memory based >> commad-response interface. Within the shared memory there is an OPAL >> command buffer and OCC response buffer that

Re: 1M hugepage size being registered on Linux

Hi Victor, Someone refreshed my memory on this, coffee was involved ... victora writes: > Hi Alistair/Jeremy, > > I am working on a bug related to 1M hugepage size being registered on > Linux (Power 8 Baremetal - Garrison). On those machines the property in the

Re: [PATCH 1/1] futex: remove duplicated code and fix UB

On Wed, Jun 21, 2017 at 01:53:18PM +0200, Jiri Slaby wrote: > There is code duplicated over all architecture's headers for > futex_atomic_op_inuser. Namely op decoding, access_ok check for uaddr, > and comparison of the result. > > Remove this duplication and leave up to the arches only the

Re: [PATCH v3 6/6] powerpc/64s: Blacklist rtas entry/exit from kprobes

On Thu, 22 Jun 2017 00:08:42 +0530 "Naveen N. Rao" wrote: > We can't take traps with relocation off, so blacklist enter_rtas() and > rtas_return_loc(). However, instead of blacklisting all of enter_rtas(), > introduce a new symbol __enter_rtas from where on we

Re: [PATCH v3 5/6] powerpc/64s: Blacklist functions invoked on a trap

On Thu, 22 Jun 2017 00:08:41 +0530 "Naveen N. Rao" wrote: > Blacklist all functions involved while handling a trap. We: > - convert some of the symbols into private symbols, > - remove the duplicate 'restore' symbol, and > - blacklist most functions involved

Re: [PATCH v3 4/6] powerpc/64s: Un-blacklist system_call() from kprobes

On Thu, 22 Jun 2017 00:08:40 +0530 "Naveen N. Rao" wrote: > It is actually safe to probe system_call() in entry_64.S, but only till > we unset MSR_RI. To allow this, add a new symbol system_call_exit() > after the mtmsrd and blacklist that. Though the mtmsrd

Re: [PATCH v3 3/6] powerpc/64s: Blacklist system_call() and system_call_common() from kprobes

On Thu, 22 Jun 2017 00:08:39 +0530 "Naveen N. Rao" wrote: > Convert some of the symbols into private symbols and blacklist > system_call_common() and system_call() from kprobes. We can't take a > trap at parts of these functions as either MSR_RI is unset or the

Re: [PATCH v3 2/6] powerpc/64s: Convert .L__replay_interrupt_return to a local label

On Thu, 22 Jun 2017 00:08:38 +0530 "Naveen N. Rao" wrote: > Commit b48bbb82e2b835 ("powerpc/64s: Don't unbalance the return branch > predictor in __replay_interrupt()") introduced __replay_interrupt_return > symbol with '.L' prefix in hopes of keeping it private.

Re: [PATCH v3 1/6] powerpc64/elfv1: Validate function pointer address in the function descriptor

On Thu, 22 Jun 2017 00:08:37 +0530 "Naveen N. Rao" wrote: > Currently, we assume that the function pointer we receive in > ppc_function_entry() points to a function descriptor. However, this is > not always the case. In particular, assembly symbols without the

[PATCH 17/17] cxlflash: Update TMF command processing

From: "Matthew R. Ochs" Currently, the SCSI command presented to the device reset handler is used to send TMFs to the AFU for a device reset. This behavior is incorrect as the command presented is an actual command and not a special notification. As such, it should

[PATCH 16/17] cxlflash: Remove zeroing of private command data

From: "Matthew R. Ochs" The SCSI core now zeroes the per-command private data area prior to calling into the LLD. Replace the clearing operation that takes place when the private command data reference is obtained with a routine that performs common initializations.

[PATCH 15/17] cxlflash: Support WS16 unmap

From: "Matthew R. Ochs" The cxlflash driver supports performing a write-same16 to scrub virtual luns when they are released by a user. To date, AFUs for adapters that are supported by cxlflash do not have the capability to unmap as part of the WS operation. This can

[PATCH 14/17] cxlflash: Support AFU debug

From: "Matthew R. Ochs" Adopt the SISLite AFU debug capability to allow future CXL Flash adapters the ability to better debug AFU issues. Update the SISLite header with the changes necessary to support AFU debug operations and create a host ioctl interface for user

[PATCH 13/17] cxlflash: Support LUN provisioning

From: "Matthew R. Ochs" Adopt the SISLite AFU LUN provisioning capability to allow future CXL Flash adapters the ability to better manage storage. Update the SISLite header with the changes necessary to support LUN provision operations and create a host ioctl interface

[PATCH 12/17] cxlflash: Refactor AFU capability checking

From: "Matthew R. Ochs" The existing AFU capability checking infrastructure is closely tied to the command mode capability bits. In order to support new capabilities, refactor the existing infrastructure to be more generic. Signed-off-by: Matthew R. Ochs

[PATCH 11/17] cxlflash: Introduce host ioctl support

From: "Matthew R. Ochs" As staging for supporting various host management functions, add a host ioctl infrastructure to filter ioctl commands and perform operations that are common for all host ioctls. Also update the cxlflash documentation to create a new section for

[PATCH 10/17] cxlflash: Separate AFU internal command handling from AFU sync specifics

From: "Matthew R. Ochs" To date the only supported internal AFU command is AFU sync. The logic to send an internal AFU command is embedded in the specific AFU sync handler and would need to be duplicated for new internal AFU commands. In order to support new internal

[PATCH 09/17] cxlflash: Create character device to provide host management interface

The cxlflash driver currently lacks host management interface. Future devices supported by cxlflash will provide a variety of host-wide management functions. Examples include LUN provisioning, hardware debug support, and firmware download. In order to provide a way to manage the device, a

[PATCH 08/17] cxlflash: Add scsi command abort handler

To date, CXL flash devices do not support a single command abort operation. Instead, the SISLite specification provides a context reset operation to cleanup all pending commands for a given context. When a context reset is successful, it is guaranteed that the AFU has aborted all currently

[PATCH 07/17] cxlflash: Flush pending commands in cleanup path

When the AFU is reset in an error path, pending scsi commands can be silently dropped without completion or a formal abort. This puts the onus on the cxlflash driver to notify mid-layer and indicating that the command can be retried. Once the card has been quiesced, the hardware send queue lock

[PATCH 06/17] cxlflash: Track pending scsi commands in each hardware queue

Currently, there is no book keeping of the pending scsi commands in the cxlflash driver. This lack of tracking in-flight requests is too restrictive and requires a heavy-hammer reset each time an adapter error is encountered. Additionally, it does not allow for commands to be properly retried. In

[PATCH 05/17] cxlflash: Handle AFU sync failures

AFU sync operations are not currently evaluated for failure. This is acceptable for paths where there is not a dependency on the AFU being consistent with the host. Examples include link reset events and LUN cleanup operations. On paths where there is a dependency, such as a LUN open, a sync

[PATCH 04/17] cxlflash: Schedule asynchronous reset of the host

A context reset failure indicates the AFU is in a bad state. At present, when such a situation occurs, no further action is taken. This leaves the adapter in an unusable state with no recoverable actions. To avoid this situation, context reset failures will be escalated to a host reset operation.

[PATCH 03/17] cxlflash: Reset hardware queue context via specified register

Per the SISLite specification, context_reset() writes 0x1 to the LSB of the reset register. When the AFU processes this reset request, it is expected to clear the bit after reset is complete. The current implementation simply checks that the entire value read back is not 1, instead of masking off

[PATCH 02/17] cxlflash: Update cxlflash_afu_sync() to return errno

The cxlflash_afu_sync() routine returns a negative one to indicate any kind of failure. This makes it impossible to establish why the error occurred. Update the return codes to clearly indicate the failure cause to the caller. Signed-off-by: Uma Krishnan ---

[PATCH 01/17] cxlflash: Combine the send queue locks

Currently there are separate spin locks for the two supported I/O queueing models. This makes it difficult to serialize with paths outside the enqueue path. As a design simplification and to support serialization with enqueue operations, move to only a single lock that is used for enqueueing

[PATCH 00/17] cxlflash: LUN provisioning support and miscellaneous fixes

This patch series contains miscellaneous fixes and several enhancements such as LUN provisioning support, WS16 unmap and AFU debug capabilities. This series is intended for 4.13 and is bisectable. Matthew R. Ochs (8): cxlflash: Separate AFU internal command handling from AFU sync specifics

[RFC v3 23/23] 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: VmFlags: rd wr mr mw me dw ac key=0 Signed-off-by: Ram Pai --- Documentation/filesystems/proc.txt | 3 ++- fs/proc/task_mmu.c | 22 +++--- 2

[RFC v3 22/23] 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 | 65 +--- 1 file changed, 45 insertions(+), 20 deletions(-) diff --git a/Documentation/vm/protection-keys.txt

[RFC v3 21/23] 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 v3 20/23] 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 v3 19/23] 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 v3 18/23] 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. This field can be used to reprogram the permission bits of any valid pkey. Similarly the value of the pkey, whose protection got violated, is made available at si_pkey field of the siginfo

[RFC v3 17/23] powerpc: Handle exceptions caused by violation of pkey protection

Handle Data and Instruction exceptions caused by memory protection-key. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/mmu_context.h | 12 + arch/powerpc/include/asm/pkeys.h | 9 arch/powerpc/include/asm/reg.h | 2 +- arch/powerpc/mm/fault.c

[RFC v3 16/23] 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 v3 15/23] 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 | 7 +++ arch/powerpc/mm/hash_utils_64.c

[RFC v3 14/23] powerpc: Implementation for sys_mprotect_pkey() system call

This system call, associates the pkey with PTE of all pages covering the given address range. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/book3s/64/pgtable.h | 22 ++- arch/powerpc/include/asm/mman.h | 14 - arch/powerpc/include/asm/pkeys.h

[RFC v3 13/23] 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 files

[RFC v3 12/23] powerpc: Implement sys_pkey_alloc and sys_pkey_free system call

Sys_pkey_alloc() allocates and returns available pkey Sys_pkey_free() frees up the pkey. Total 32 keys are supported on powerpc. However pkey 0,1 and 31 are reserved. So effectively we have 29 pkeys. Each key can be initialized to disable read, write and execute permissions. On powerpc a

[RFC v3 11/23] x86: key creation with PKEY_DISABLE_EXECUTE is disallowed

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

[RFC v3 10/23] mm: provide the ability to disable execute 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 v3 09/23] 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 v3 08/23] powerpc: use helper functions in flush_hash_page()

replace redundant code in flush_hash_page() with helper functions get_hidx_gslot() and set_hidx_slot() Signed-off-by: Ram Pai --- arch/powerpc/mm/hash_utils_64.c | 13 - 1 file changed, 4 insertions(+), 9 deletions(-) diff --git

[RFC v3 07/23] powerpc: use helper functions in __hash_page_4K() for 4K PTE

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

[RFC v3 06/23] powerpc: use helper functions in __hash_page_4K() for 64K PTE

replace redundant code in __hash_page_4K() with helper functions get_hidx_gslot() and set_hidx_slot() Signed-off-by: Ram Pai --- arch/powerpc/mm/hash64_64k.c | 24 ++-- 1 file changed, 6 insertions(+), 18 deletions(-) diff --git

[RFC v3 05/23] 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 file changed, 2 insertions(+), 1 deletion(-) diff --git

[RFC v3 04/23] 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 that is backed by 64K

[RFC v3 03/23] powerpc: introduce get_hidx_gslot helper

Introduce get_hidx_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 | 3 +++

[RFC v3 02/23] powerpc: introduce set_hidx_slot helper

Introduce set_hidx_slot() which sets the (H_PAGE_F_SECOND|H_PAGE_F_GIX) bits at the appropriate location in the PTE of 4K PTE. In the case of 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 take some

[RFC v3 01/23] 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

[RFC v3 00/23] 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 a address range withinits address space. The process than can dynamically set

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

On Wed, 2017-06-21 at 14:45 -0300, Thiago Jung Bauermann wrote: > Hello Mimi, > > Thanks for your review, and for queuing the other patches in this series. > > Mimi Zohar writes: > > On Wed, 2017-06-07 at 22:49 -0300, Thiago Jung Bauermann wrote: > >> This patch

Re: [PATCH] powerpc: Only obtain cpu_hotplug_lock if called by rtasd

Michael Ellerman writes: > Thiago Jung Bauermann writes: > >> Calling arch_update_cpu_topology from a CPU hotplug state machine callback >> hits a deadlock because the function tries to get a read lock on >> cpu_hotplug_lock while the state

Re: [PATCH V4 2/2] powerpc/powernv : Add support for OPAL-OCC command/response interface

On Wed, 2017-06-21 at 13:36 +0530, Shilpasri G Bhat wrote: > In P9, OCC (On-Chip-Controller) supports shared memory based > commad-response interface. Within the shared memory there is an OPAL > command buffer and OCC response buffer that can be used to send > inband commands to OCC. This patch

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

Hi all, On Tue, 13 Jun 2017 09:56:41 -0400 Tejun Heo wrote: > > (forwarding to Li w/ full body) > > Li, can you please take a look at this? > > Thanks. > > On Mon, Jun 12, 2017 at 04:53:42PM +0530, Abdul Haleem wrote: > > Hi, > > > > linux-next kernel crashed while running

Re: [PATCH v6 1/4] of: remove *phandle properties from expanded device tree

adding Ben and Paul. Hi Michael, On 06/20/17 21:57, Michael Ellerman wrote: > Hi Frank, > > frowand.l...@gmail.com writes: >> From: Frank Rowand >> >> Remove "phandle", "linux,phandle", and "ibm,phandle" properties from >> the internal device tree. The phandle will

Re: [next-20170609] WARNING: CPU: 3 PID: 71167 at lib/idr.c:157 idr_replace

Quoting Tejun Heo (2017-06-13 14:58:49) > Cc'ing David Airlie. > > This is from drm driver calling in idr_replace() w/ a negative id. > Probably a silly bug in error handling path? No, this is the validation of an invalid userspace handle. The drm ABI for handles is supposed to be a full u32

Re: [PATCH v6 2/4] of: make __of_attach_node() static

On 06/20, frowand.l...@gmail.com wrote: > From: Frank Rowand > > __of_attach_node() is not used outside of drivers/of/dynamic.c. Make > it static and remove it from drivers/of/of_private.h. > > Signed-off-by: Frank Rowand > --- Reviewed-by:

Re: Network TX Stall on 440EP Processor

On Tue, 2017-06-20 at 14:17 -0700, Thomas Besemer wrote: > I'm working on a project that is derived from the Yosemite > PPC 440EP board.  It's a legacy project that was running the > 2.6.24 Kernel, and network traffic was stalling due to transmission > halting without an understandable error (in

Re: [next-20170609] WARNING: CPU: 3 PID: 71167 at lib/idr.c:157 idr_replace

Cc'ing dri-devel. Dave. On Tue, 13 Jun 2017, Tejun Heo wrote: > Cc'ing David Airlie. > > This is from drm driver calling in idr_replace() w/ a negative id. > Probably a silly bug in error handling path? > > Thanks. > > On Mon, Jun 12, 2017 at 08:10:54PM +0530, Abdul Haleem wrote: > > Hi, >

Re: Network TX Stall on 440EP Processor

Hi Michael - > > Thomas Besemer writes: > > I'm working on a project that is derived from the Yosemite > > PPC 440EP board. It's a legacy project that was running the > > 2.6.24 Kernel, and network traffic was stalling due to transmission > > halting without an

Re: clean up and modularize arch dma_mapping interface V2

On 06/16/2017 11:10 AM, Christoph Hellwig wrote: Hi all, for a while we have a generic implementation of the dma mapping routines that call into per-arch or per-device operations. But right now there still are various bits in the interfaces where don't clearly operate on these ops. This

Re: [RFC v2 02/12] powerpc: Free up four 64K PTE bits in 64K backed hpte pages.

On Wed, Jun 21, 2017 at 12:24:34PM +0530, Aneesh Kumar K.V wrote: > Ram Pai writes: > > > > > diff --git a/arch/powerpc/mm/hugetlbpage-hash64.c > > b/arch/powerpc/mm/hugetlbpage-hash64.c > > index a84bb44..239ca86 100644 > > --- a/arch/powerpc/mm/hugetlbpage-hash64.c

Re: [PATCH v6 1/4] of: remove *phandle properties from expanded device tree

On 06/20/17 23:18, Frank Rowand wrote: > Hi Rob, > > Michael has an issue that means this patch series is not OK in the > current form. I will work on a v7 to see if I can resolve the > issue. > > -Frank < snip > Hi Rob, The issue is in patch 1. Patches 2 - 4 are small independent patches

Re: [PATCH] powerpc: Convert VDSO update function to use new update_vsyscall interface

On Sat, May 27, 2017 at 1:04 AM, Paul Mackerras wrote: > This converts the powerpc VDSO time update function to use the new > interface introduced in commit 576094b7f0aa ("time: Introduce new > GENERIC_TIME_VSYSCALL", 2012-09-11). Where the old interface gave > us the time as

[PATCH 2/2] selftests/ftrace: Update multiple kprobes test for powerpc

KPROBES_ON_FTRACE is only available on powerpc64le. Update comment to clarify this. Also, we should use an offset of 8 to ensure that the probe does not fall on ftrace location. The current offset of 4 will fall before the function local entry point and won't fire, while an offset of 12 or 16

[PATCH 1/2] trace/kprobes: Sanitize derived event names

When we derive event names, convert some expected symbols (such as ':' used to specify module:name and '.' present in some symbols) into underscores so that the event name is not rejected. Before this patch: # echo 'p kobject_example:foo_store' > kprobe_events trace_kprobe: Failed to

[PATCH 0/2] A couple of small updates/fixes for kprobes tracer

Two simple updates for kprobes tracer: - the first patch is a convenience and allows to probe module symbols as well as any dot symbols (necessary on powerpc64 elfv1) without having to provide a name for the probepoint. - the second patch updates the newly added multiple_kprobes.tc test case

[PATCH v3 6/6] powerpc/64s: Blacklist rtas entry/exit from kprobes

We can't take traps with relocation off, so blacklist enter_rtas() and rtas_return_loc(). However, instead of blacklisting all of enter_rtas(), introduce a new symbol __enter_rtas from where on we can't take a trap and blacklist that. Signed-off-by: Naveen N. Rao

[PATCH v3 5/6] powerpc/64s: Blacklist functions invoked on a trap

Blacklist all functions involved while handling a trap. We: - convert some of the symbols into private symbols, - remove the duplicate 'restore' symbol, and - blacklist most functions involved while handling a trap. Reviewed-by: Masami Hiramatsu Signed-off-by: Naveen N. Rao

[PATCH v3 4/6] powerpc/64s: Un-blacklist system_call() from kprobes

It is actually safe to probe system_call() in entry_64.S, but only till we unset MSR_RI. To allow this, add a new symbol system_call_exit() after the mtmsrd and blacklist that. Though the mtmsrd instruction itself is now whitelisted, we won't be allowed to probe on it as we don't allow probing on

[PATCH v3 3/6] powerpc/64s: Blacklist system_call() and system_call_common() from kprobes

Convert some of the symbols into private symbols and blacklist system_call_common() and system_call() from kprobes. We can't take a trap at parts of these functions as either MSR_RI is unset or the kernel stack pointer is not yet setup. Reviewed-by: Masami Hiramatsu

[PATCH v3 2/6] powerpc/64s: Convert .L__replay_interrupt_return to a local label

Commit b48bbb82e2b835 ("powerpc/64s: Don't unbalance the return branch predictor in __replay_interrupt()") introduced __replay_interrupt_return symbol with '.L' prefix in hopes of keeping it private. However, due to the use of LOAD_REG_ADDR(), the assembler kept this symbol visible. Fix the same

[PATCH v3 1/6] powerpc64/elfv1: Validate function pointer address in the function descriptor

Currently, we assume that the function pointer we receive in ppc_function_entry() points to a function descriptor. However, this is not always the case. In particular, assembly symbols without the right annotation do not have an associated function descriptor. Some of these symbols are added to

[PATCH v3 0/6] powerpc: build out kprobes blacklist -- series 3

This is the third in the series of patches to build out an appropriate kprobes blacklist for powerpc. Since posting the second series (*), there have been related changes to the code and I have brought that series forward to account for those changes. As such, all patches from the second series

Re: [GIT PULL 00/25] perf/core improvements and fixes

; Merge tag 'perf-core-for-mingo-4.13-20170719' of > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core > (2017-06-20 10:49:08 +0200) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git >

[PATCH 06/25] perf unwind: Support for powerpc

From: Paolo Bonzini Porting PPC to libdw only needs an architecture-specific hook to move the register state from perf to libdw. The ARM and x86 architectures already use libdw, and it is useful to have as much common code for the unwinder as possible. Mark Wielaard has

[GIT PULL 00/25] perf/core improvements and fixes

into perf/core (2017-06-20 10:49:08 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-core-for-mingo-4.13-20170621 for you to fetch changes up to 701516ae3dec801084bc913d21e03fce15c61a0b: perf script: Fix message because field

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

Hello Mimi, Thanks for your review, and for queuing the other patches in this series. Mimi Zohar writes: > On Wed, 2017-06-07 at 22:49 -0300, Thiago Jung Bauermann wrote: >> This patch introduces the modsig keyword to the IMA policy syntax to >> specify that a given

Re: 1M hugepage size being registered on Linux

On 06/21/2017 07:33 AM, Michael Ellerman wrote: I am working on a bug related to 1M hugepage size being registered on Linux (Power 8 Baremetal - Garrison). Wasn't that caused by a firmware bug? Ben/Stewart, does that ring a bell, something new, intended or not? :- ) Thanks, I was

Re: [PATCH v2] perf: libdw support for powerpc [ping]

Em Wed, Jun 21, 2017 at 04:19:11PM +0200, Milian Wolff escreveu: > On Mittwoch, 21. Juni 2017 14:48:29 CEST Arnaldo Carvalho de Melo wrote: > > Em Wed, Jun 21, 2017 at 10:16:56AM +0200, Milian Wolff escreveu: > > > On Mittwoch, 21. Juni 2017 03:07:39 CEST Arnaldo Carvalho de Melo wrote: > > > > Hi

Re: [PATCH V6 1/2] powerpc/hotplug: Ensure enough nodes avail for operations

On 06/21/2017 04:52 AM, Michael Ellerman wrote: > Michael Bringmann writes: > >> powerpc/hotplug: On systems like PowerPC which allow 'hot-add' of CPU >> or memory resources, it may occur that the new resources are to be >> inserted into nodes that were not used for

Re: [PATCH v2] perf: libdw support for powerpc [ping]

On Mittwoch, 21. Juni 2017 14:48:29 CEST Arnaldo Carvalho de Melo wrote: > Em Wed, Jun 21, 2017 at 10:16:56AM +0200, Milian Wolff escreveu: > > On Mittwoch, 21. Juni 2017 03:07:39 CEST Arnaldo Carvalho de Melo wrote: > > > Hi Millian, can I take this as an Acked-by or Tested-by? > > > > I have no

Re: [PATCH V6 0/2] powerpc/dlpar: Correct display of hot-add/hot-remove CPUs and memory

One of the patches was doubled and sent twice yesterday. Will update number regardless in future. On 06/21/2017 04:54 AM, Michael Ellerman wrote: > Michael Bringmann writes: > >> On Power systems with shared configurations of CPUs and memory, there >> are some issues

Re: new dma-mapping tree, was Re: clean up and modularize arch dma_mapping interface V2

Hi Christoph, On 2017-06-20 15:16, Christoph Hellwig wrote: On Tue, Jun 20, 2017 at 11:04:00PM +1000, Stephen Rothwell wrote: git://git.linaro.org/people/mszyprowski/linux-dma-mapping.git#dma-mapping-next Contacts: Marek Szyprowski and Kyungmin Park (cc'd) I have called your tree

Re: [PATCH v2] perf: libdw support for powerpc [ping]

Em Wed, Jun 21, 2017 at 10:16:56AM +0200, Milian Wolff escreveu: > On Mittwoch, 21. Juni 2017 03:07:39 CEST Arnaldo Carvalho de Melo wrote: > > Hi Millian, can I take this as an Acked-by or Tested-by? > I have no access to any PowerPC hardware. In principle the code looks > fine, but that's all

[PATCH 1/1] futex: remove duplicated code and fix UB

There is code duplicated over all architecture's headers for futex_atomic_op_inuser. Namely op decoding, access_ok check for uaddr, and comparison of the result. Remove this duplication and leave up to the arches only the needed assembly which is now in arch_futex_atomic_op_inuser. This

Re: 1M hugepage size being registered on Linux

victora writes: > Hi Alistair/Jeremy, > > I am working on a bug related to 1M hugepage size being registered on > Linux (Power 8 Baremetal - Garrison). Wasn't that caused by a firmware bug? > I was checking dmesg and it seems that 1M page size is coming from >

Re: Network TX Stall on 440EP Processor

Hi Thomas, Thomas Besemer writes: > I'm working on a project that is derived from the Yosemite > PPC 440EP board. It's a legacy project that was running the > 2.6.24 Kernel, and network traffic was stalling due to transmission > halting without an understandable error

Re: [PATCH] powerpc: Only obtain cpu_hotplug_lock if called by rtasd

Thiago Jung Bauermann writes: > Calling arch_update_cpu_topology from a CPU hotplug state machine callback > hits a deadlock because the function tries to get a read lock on > cpu_hotplug_lock while the state machine still holds a write lock on it. > > Since all

[PATCH V3] cxl: Export library to support IBM XSL

This patch exports a in-kernel 'library' API which can be called by other drivers to help interacting with an IBM XSL on a POWER9 system. The XSL (Translation Service Layer) is a stripped down version of the PSL (Power Service Layer) used in some cards such as the Mellanox CX5. Like the PSL, it

Re: [PATCH V6 0/2] powerpc/dlpar: Correct display of hot-add/hot-remove CPUs and memory

Michael Bringmann writes: > On Power systems with shared configurations of CPUs and memory, there > are some issues with association of additional CPUs and memory to nodes > when hot-adding resources. These patches address some of those problems. > > powerpc/hotplug: On

Re: [PATCH V6 1/2] powerpc/hotplug: Ensure enough nodes avail for operations

Michael Bringmann writes: > powerpc/hotplug: On systems like PowerPC which allow 'hot-add' of CPU > or memory resources, it may occur that the new resources are to be > inserted into nodes that were not used for these resources at bootup. > In the kernel, any node that

Re: [PATCH] powerpc: dts: use #include "..." to include local DT

Masahiro Yamada writes: > 2017-06-14 15:45 GMT+09:00 Michael Ellerman : >> >> Acked-by: Michael Ellerman > > I have not seen it in linux-next yet. > > Who will pick it up? In the original patch you said: Fix them to

Re: [RFC v2 01/12] powerpc: Free up four 64K PTE bits in 4K backed hpte pages.

On Wed, Jun 21, 2017 at 12:11:32PM +0530, Aneesh Kumar K.V wrote: > Ram Pai writes: > > > 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

Re: [PATCH v2] perf: libdw support for powerpc [ping]

On Mittwoch, 21. Juni 2017 03:07:39 CEST Arnaldo Carvalho de Melo wrote: > Em Thu, Jun 15, 2017 at 10:46:16AM +0200, Milian Wolff escreveu: > > On Tuesday, June 13, 2017 5:55:09 PM CEST Ravi Bangoria wrote: > > Just a quick question: Have you guys applied my recent patch: > > > > commit

Re: [PATCH] powerpc/64: Initialise thread_info for emergency stacks

e: > > http://marc.info/?l=linuxppc-embedded=149794320519941=2 > > arch/powerpc/include/asm/thread_info.h | 19 +++ > arch/powerpc/kernel/setup_64.c | 6 +++--- > 2 files changed, 22 insertions(+), 3 deletions(-) Hi Nicholas, Thanks for the patch, Ve

Re: [RFC v2 07/12] powerpc: Macro the mask used for checking DSI exception

On Wed, Jun 21, 2017 at 12:55:42PM +0530, Aneesh Kumar K.V wrote: > Ram Pai writes: > > > 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

[PATCH V4 2/2] powerpc/powernv : Add support for OPAL-OCC command/response interface

In P9, OCC (On-Chip-Controller) supports shared memory based commad-response interface. Within the shared memory there is an OPAL command buffer and OCC response buffer that can be used to send inband commands to OCC. This patch adds a platform driver to support the command/response interface

  1   2   >