Re: [PATCH v3] kernel/module_64.c: Add REL24 relocation support of livepatch symbols

Josh Poimboeuf writes: > On Tue, Nov 07, 2017 at 12:31:05PM +0100, Torsten Duwe wrote: >> On Tue, Nov 07, 2017 at 07:34:29PM +1100, Michael Ellerman wrote: >> > > So, just brainstorming a bit, here are the possible solutions I can >> > > think of: >> > > >> > > a) Create a

Re: [PATCH v3 13/18] powerpc: Add support for setting SPRN_TIDR

Sukadev Bhattiprolu writes: > diff --git a/arch/powerpc/kernel/process.c b/arch/powerpc/kernel/process.c > index 37ed60b..d861fcd 100644 > --- a/arch/powerpc/kernel/process.c > +++ b/arch/powerpc/kernel/process.c > @@ -1120,6 +1120,13 @@ static inline void

[PATCH v3] powerpc/kernel/sysfs: Export ldbar spr to sysfs

Add ldbar spr to sysfs. The spr holds thread level In-Memory Collection (IMC) counter configuration data. Exposing this will help to understand the current configuration of thread-level counters in the system. Primarily, Bit 0 of ldbar says whether the counters are enabled

[PATCH] powerpc/powernv: Fix IMC_MAX_PMU macro

IMC_MAX_PMU is used for static storage (per_nest_pmu_arr) which holds nest pmu information. Current value for the macro is 32 based on the initial number of nest pmu units supported by the nest microcode. Currently 29 nest units are enabled based on the system configuration. But going forward,

Re: [PATCH v2 14/18] powerpc: Define set_thread_used_vas()

Sukadev Bhattiprolu writes: > diff --git a/arch/powerpc/kernel/process.c b/arch/powerpc/kernel/process.c > index d861fcd..cb5f108 100644 > --- a/arch/powerpc/kernel/process.c > +++ b/arch/powerpc/kernel/process.c > @@ -1234,17 +1234,17 @@ struct task_struct

Re: [PATCH v3] kernel/module_64.c: Add REL24 relocation support of livepatch symbols

Josh Poimboeuf wrote: On Tue, Nov 07, 2017 at 12:31:05PM +0100, Torsten Duwe wrote: On Tue, Nov 07, 2017 at 07:34:29PM +1100, Michael Ellerman wrote: > > So, just brainstorming a bit, here are the possible solutions I can > > think of: > > > > a) Create a special klp stub for such calls (as in

[PATCH v3] powerpc/kernel/sysfs: Export ldbar spr to sysfs

Add ldbar spr to sysfs. The spr holds thread level In-Memory Collection (IMC) counter configuration data. Exposing this will help to understand the current configuration of thread-level counters in the system. Primarily, Bit 0 of ldbar says whether the counters are enabled

[PATCH v5 1/3] powerpc/kernel: Separate SR-IOV Calls

SR-IOV can now be enabled in PowerNV platforms and Pseries platforms. Therefore, the appropriate calls were moved to machine dependent code instead of definition at compile time. Signed-off-by: Bryant G. Ly Signed-off-by: Juan J. Alvarez ---

[PATCH v5 0/3] Prepartion for SR-IOV PowerVM Enablement

v1 - Initial patch v2 - Addressed Bjorn's comment on creating a highly platform dependent global exported symbol. v3 - Based patch off linux-ppc/master v4 - Using the sriov-drivers_autoprobe mechanism per Bjorn's request v5 - Fixed comments and commit message Bryant G. Ly (3):

[PATCH v5 2/3] pseries: Add PSeries SR-IOV Machine dependent calls

Add calls for PSeries platform to configure/deconfigure SR-IOV. Signed-off-by: Bryant G. Ly Signed-off-by: Juan J. Alvarez --- arch/powerpc/platforms/pseries/eeh_pseries.c | 24 +++ arch/powerpc/platforms/pseries/pci.c

[PATCH v5 3/3] PCI/IOV: Add pci_vf_drivers_autoprobe() interface

Add a pci_vf_drivers_autoprobe() interface. Setting autoprobe to false on the PF prevents drivers from binding to VFs when they are enabled. Signed-off-by: Bryant G. Ly Signed-off-by: Juan J. Alvarez Acked-by: Bjorn Helgaas

Re: [PATCH v3] powerpc/kernel/sysfs: Export ldbar spr to sysfs

Hi, Kindly ignore this patch, I send a wrong version. Will send out the right one. Thanks, Anju On Thursday 09 November 2017 05:43 PM, Anju T Sudhakar wrote: Add ldbar spr to sysfs. The spr holds thread level In-Memory Collection (IMC) counter configuration data. Exposing this will help

Re: [PATCH v3] kernel/module_64.c: Add REL24 relocation support of livepatch symbols

On Thu, Nov 09, 2017 at 04:49:05PM +0530, Naveen N. Rao wrote: > > > > > d) Have kpatch-build do some other kind of transformation? For > > > > > example, > > > > >maybe it could generate klp stubs which the callee calls into. > > > > > Each > > > > >klp stub could then do a proper

Re: [PATCH] fbdev: controlfb: Add missing modes to fix out of bounds access

On Tuesday, November 07, 2017 03:05:05 PM Geert Uytterhoeven wrote: > Dan's static analysis says: > > drivers/video/fbdev/controlfb.c:560 control_setup() > error: buffer overflow 'control_mac_modes' 20 <= 21 > > Indeed, control_mac_modes[] has only 20 elements, while VMODE_MAX is 22, >

[PATCH v2 0/5] powerpc VA allocator fixes for 512TB support

After clarifying the intended semantics, the previous patch series went the wrong way with MAP_FIXED handling, so I fixed that. This series is not quite ready for merge. I prefer to see what x86 does exactly because it also has some fixes to make. But time is becoming short before 4.14, so I'd

[PATCH v2 5/5] powerpc/64s: mm_context.addr_limit is only used on hash

Radix keeps no meaningful state in addr_limit, so remove it from radix code and rename to slb_addr_limit to make it clear it applies to hash only. Signed-off-by: Nicholas Piggin --- arch/powerpc/include/asm/book3s/64/mmu-hash.h | 2 +-

[PATCH v2 3/5] powerpc/64s/hash: Allow MAP_FIXED allocations to cross 128TB boundary

While mapping hints with a length that cross 128TB are disallowed, MAP_FIXED allocations that cross 128TB are allowed. These are failing on hash (on radix they succeed). Add an additional case for fixed mappings to expand the addr_limit when crossing 128TB. Cc: "Aneesh Kumar K.V"

[PATCH v2 1/5] powerpc/64s/hash: Fix 128TB-512TB virtual address boundary case allocation

When allocating VA space with a hint that crosses 128TB, the SLB addr_limit variable is not expanded if addr is not > 128TB, but the slice allocation looks at task_size, which is 512TB. This results in slice_check_fit() incorrectly succeeding because the slice_count truncates off bit 128 of the

Re: POWER: Unexpected fault when writing to brk-allocated memory

On Tue, 7 Nov 2017 17:01:58 +0300 "Kirill A. Shutemov" wrote: > On Tue, Nov 07, 2017 at 07:15:58PM +0530, Aneesh Kumar K.V wrote: > > > > > > > > If it is decided to keep these kind of heuristics, can we get just a > > > small but reasonably precise description of each

[PATCH v2 2/5] powerpc/64s/hash: Fix fork() with 512TB process address space

Hash unconditionally resets the addr_limit to default (128TB) when the mm context is initialised. If a process has > 128TB mappings when it forks, the child will not get the 512TB addr_limit, so accesses to valid > 128TB mappings will fail in the child. Fix this by only resetting the addr_limit

[PATCH v2 4/5] powerpc/64s/radix: Fix 128TB-512TB virtual address boundary case allocation

Radix VA space allocations test addresses against mm->task_size which is 512TB, even in cases where the intention is to limit allocation to below 128TB. This results in mmap with a hint address below 128TB but address + length above 128TB succeeding when it should fail (as hash does after the

Re: [GIT PULL] Please pull JSON files for POWR9 PMU events

Em Wed, Nov 08, 2017 at 12:19:38PM -0800, Sukadev Bhattiprolu escreveu: > Hi Arnaldo, > > Please pull an update to the JSON files for POWER9 PMU events. > > The following changes since commit 148b43a3540bf25875bb5ab695a446950dc8d559: > > tools headers: Synchronize kernel ABI headers wrt SPDX

Re: POWER: Unexpected fault when writing to brk-allocated memory

On Fri, Nov 10, 2017 at 04:15:26AM +1100, Nicholas Piggin wrote: > So these semantics are what we're going with? Anything that does mmap() is > guaranteed of getting a 47-bit pointer and it can use the top 17 bits for > itself? Is intended to be cross-platform or just x86 and power specific? It

Re: [PATCH] [net-next,v3] ibmvnic: Feature implementation of Vital Product Data (VPD) for the ibmvnic driver

On 11/09/2017 11:00 AM, Desnes Augusto Nunes do Rosario wrote: This patch implements and enables VDP support for the ibmvnic driver. Moreover, it includes the implementation of suitable structs, signal transmission/handling and functions which allows the retrival of firmware information

Re: [PATCH v9 44/51] selftest/vm: powerpc implementation for generic abstraction

Hi Ram, On Mon, Nov 06, 2017 at 12:57:36AM -0800, Ram Pai wrote: > @@ -206,12 +209,14 @@ void signal_handler(int signum, siginfo_t *si, void > *vucontext) > > trapno = uctxt->uc_mcontext.gregs[REG_TRAPNO]; > ip = uctxt->uc_mcontext.gregs[REG_IP_IDX]; > - fpregset =

[PATCH] [net-next, v3] ibmvnic: Feature implementation of Vital Product Data (VPD) for the ibmvnic driver

This patch implements and enables VDP support for the ibmvnic driver. Moreover, it includes the implementation of suitable structs, signal transmission/handling and functions which allows the retrival of firmware information from the ibmvnic card through the ethtool command. Signed-off-by:

Re: [PATCH] [net-next,v3] ibmvnic: Feature implementation of Vital Product Data (VPD) for the ibmvnic driver

On 11/09/2017 01:00 PM, Desnes Augusto Nunes do Rosario wrote: > This patch implements and enables VDP support for the ibmvnic driver. > Moreover, it includes the implementation of suitable structs, signal > transmission/handling and functions which allows the retrival of firmware > information

Re: [PATCH] powerpc/powernv: Fix IMC_MAX_PMU macro

Anju T Sudhakar writes: > IMC_MAX_PMU is used for static storage (per_nest_pmu_arr) which holds > nest pmu information. Current value for the macro is 32 based on > the initial number of nest pmu units supported by the nest microcode. > Currently 29 nest units are

Re: [PATCH v2] powerpc/powernv: Add pci_reset_phbs parameter to issue a PHB reset

On 10/25/2017 01:27 PM, Guilherme G. Piccoli wrote: > During a kdump kernel boot in PowerPC, we request a reset of the PHBs > to the FW. It makes sense, since if we are booting a kdump kernel it > means we had some trouble before and we cannot rely in the adapters' > health; they could be in a bad

Re: [PATCH v9 00/51] powerpc, mm: Memory Protection Keys

On Mon, Nov 06, 2017 at 05:22:18PM -0800, Ram Pai wrote: > On Mon, Nov 06, 2017 at 10:28:41PM +0100, Florian Weimer wrote: > > * Ram Pai: > > > > > Testing: > > > --- > > > This patch series has passed all the protection key > > > tests available in the selftest directory.The > > > tests are

Re: [PATCH v9 44/51] selftest/vm: powerpc implementation for generic abstraction

On Thu, Nov 09, 2017 at 04:47:15PM -0200, Breno Leitao wrote: > Hi Ram, > > On Mon, Nov 06, 2017 at 12:57:36AM -0800, Ram Pai wrote: > > @@ -206,12 +209,14 @@ void signal_handler(int signum, siginfo_t *si, void > > *vucontext) > > > > trapno = uctxt->uc_mcontext.gregs[REG_TRAPNO]; > >

[PATCHv4 3/6] powerpc64: Add .opd based function descriptor dereference

We are moving towards separate kernel and module function descriptor dereference callbacks. This patch enables it for powerpc64. For pointers that belong to the kernel - Added __start_opd and __end_opd pointers, to track the kernel .opd section address range; - Added

[PATCHv4 0/6] printk/ia64/ppc64/parisc64: let's deprecate %pF/%pf printk specifiers

Hello, A reworked version. There is a new dereference_symbol_descriptor() function now, where "the magic happens", so I don't touch kallsyms_lookup() and module_address_lookup() anymore. All Ack-s/Tested-by-s were dropped, since the patch set has been reworked. I'm kindly

[PATCHv4 4/6] parisc64: Add .opd based function descriptor dereference

We are moving towards separate kernel and module function descriptor dereference callbacks. This patch enables it for parisc64. For pointers that belong to the kernel - Added __start_opd and __end_opd pointers, to track the kernel .opd section address range; - Added

[PATCHv4 6/6] checkpatch: add pF/pf deprecation warning

We deprecated '%pF/%pf' printk specifiers, since '%pS/%ps' is now smart enough to handle function pointer dereference on platforms where such dereference is required. Signed-off-by: Sergey Senozhatsky Signed-off-by: Joe Perches Cc: Andy Whitcroft

[PATCHv4 2/6] ia64: Add .opd based function descriptor dereference

We are moving towards separate kernel and module function descriptor dereference callbacks. This patch enables it for IA64. For pointers that belong to the kernel - Added __start_opd and __end_opd pointers, to track the kernel .opd section address range; - Added

[PATCHv4 5/6] symbol lookup: introduce dereference_symbol_descriptor()

dereference_symbol_descriptor() invokes appropriate ARCH specific function descriptor dereference callbacks: - dereference_kernel_function_descriptor() if the pointer is a kernel symbol; - dereference_module_function_descriptor() if the pointer is a module symbol. This is the last step

[PATCHv4 1/6] sections: split dereference_function_descriptor()

There are two format specifiers to print out a pointer in symbolic format: '%pS/%ps' and '%pF/%pf'. On most architectures, the two mean exactly the same thing, but some architectures (ia64, ppc64, parisc64) use an indirect pointer for C function pointers, where the function pointer points to a

[PATCHv3 1/3] ARMv8: dts: ls1046a: add the property of IB and OB

Add the property of inbound and outbound windows number for ep driver. Signed-off-by: Bao Xiaowei Acked-by: Minghuan Lian --- v2: - no change v3: - modify the commit message arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 6 ++ 1 file

[PATCHv3 0/3] dts: Add the property of IB and OB

Depend on http://patchwork.ozlabs.org/patch/815382/ Bao Xiaowei (3): ARMv8: dts: ls1046a: add the property of IB and OB ARMv8: layerscape: add the pcie ep function support ARMv8: pcie: make the DWC EP driver support for layerscape arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 6 ++

[PATCHv3 2/3] ARMv8: layerscape: add the pcie ep function support

Add the pcie controller ep function support of layerscape base on pcie ep framework. Signed-off-by: Bao Xiaowei --- v2: - fix the ioremap function used but no ioumap issue - optimize the code structure - add code comments v3: - fix the msi outband window request

Re: [PATCH] powerpc/powernv: Fix IMC_MAX_PMU macro

On Friday 10 November 2017 02:32 AM, Michael Ellerman wrote: Anju T Sudhakar writes: IMC_MAX_PMU is used for static storage (per_nest_pmu_arr) which holds nest pmu information. Current value for the macro is 32 based on the initial number of nest pmu units supported

Re: POWER: Unexpected fault when writing to brk-allocated memory

On Thu, 9 Nov 2017 11:44:21 -0800 Matthew Wilcox wrote: > On Fri, Nov 10, 2017 at 04:15:26AM +1100, Nicholas Piggin wrote: > > So these semantics are what we're going with? Anything that does mmap() is > > guaranteed of getting a 47-bit pointer and it can use the top 17 bits

Re: [PATCH v3] kernel/module_64.c: Add REL24 relocation support of livepatch symbols

On Fri, Nov 10, 2017 at 2:19 AM, Josh Poimboeuf wrote: > On Thu, Nov 09, 2017 at 04:49:05PM +0530, Naveen N. Rao wrote: >> > > > > d) Have kpatch-build do some other kind of transformation? For >> > > > > example, >> > > > >maybe it could generate klp stubs which the

[PATCHv3 3/3] ARMv8: pcie: make the DWC EP driver support for layerscape

Layerscape pcie controllers support RC or EP mode, Add the EP mode support in Kconfig, the driver will support both RC and EP mode, and the driver is able to judge the pcie controllers work on RC or EP mode. Signed-off-by: Bao Xiaowei Acked-by: Minghuan Lian

RE: [PATCHv3 2/3] ARMv8: layerscape: add the pcie ep function support

> -Original Message- > From: Bao Xiaowei [mailto:xiaowei@nxp.com] > Sent: Friday, November 10, 2017 10:49 AM > To: robh...@kernel.org; mark.rutl...@arm.com; catalin.mari...@arm.com; > will.dea...@arm.com; bhelg...@google.com; shawn...@kernel.org; > Madalin-cristian Bucur

Re: [PATCH v3] kernel/module_64.c: Add REL24 relocation support of livepatch symbols

On Fri, Nov 10, 2017 at 01:06:25PM +1100, Balbir Singh wrote: > On Fri, Nov 10, 2017 at 2:19 AM, Josh Poimboeuf wrote: > > FWIW, I think it won't matter anyway. I'm currently pursuing the option > > of inserting nops after local calls, because it has less runtime > >

[PATCHv4 1/3] ARMv8: dts: ls1046a: add the property of IB and OB

Add the property of inbound and outbound windows number for ep driver. Signed-off-by: Bao Xiaowei Acked-by: Minghuan Lian --- v2: - no change v3: - modify the commit message v4: - no change arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 6

[PATCHv4 0/3] dts: Add the property of IB and OB

Depend on http://patchwork.ozlabs.org/patch/815382/ Bao Xiaowei (3): ARMv8: dts: ls1046a: add the property of IB and OB ARMv8: layerscape: add the pcie ep function support ARMv8: pcie: make the DWC EP driver support for layerscape arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 6 ++

[PATCHv4 3/3] ARMv8: pcie: make the DWC EP driver support for layerscape

Layerscape pcie controllers support RC or EP mode, Add the EP mode support in Kconfig, the driver will support both RC and EP mode, and the driver is able to judge the pcie controllers work on RC or EP mode. Signed-off-by: Bao Xiaowei Acked-by: Minghuan Lian

[PATCH] powerpc/64s/slice: Use addr limit when computing slice mask

While computing slice mask for the free area we need make sure we only search in the addr limit applicable for this mmap. We update the slb_addr_limit after we request for a mmap above 128TB. But the following mmap request with hint addr below 128TB should still limit its search to below 128TB.

[PATCHv4 2/3] ARMv8: layerscape: add the pcie ep function support

Add the pcie controller ep function support of layerscape base on pcie ep framework. Signed-off-by: Bao Xiaowei --- v2: - fix the ioremap function used but no ioumap issue - optimize the code structure - add code comments v3: - fix the msi outband window request failed

Re: [PATCH v2] powerpc64/exceptions: Refactor code to eliminate a few memory loads

"Naveen N. Rao" writes: > On 2017/06/19 03:21PM, Aneesh Kumar K.V wrote: >> > @@ -1445,8 +1446,8 @@ do_hash_page: >> > handle_page_fault: >> >andis. r0,r4,DSISR_DABRMATCH@h >> >bne-handle_dabr_fault >> > - ld r4,_DAR(r1) >> > - ld