Re: [PATCH] kernel/kprobes: Add test to validate pt_regs

On Wed, 14 Jun 2017 11:40:08 +0900 Masami Hiramatsu wrote: > On Fri, 9 Jun 2017 00:53:08 +0530 > "Naveen N. Rao" wrote: > > > Add a test to verify that the registers passed in pt_regs on kprobe > > (trap), optprobe (jump) and

Re: RESEND Re: [Patch 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc

On Wed, Jun 14, 2017 at 8:21 AM, Michael Bringmann wrote: > On a related note, we are discussing the addition of 2 new device-tree > properties > with Pete Heyrman and his fellows that should simplify the determination > of the > set of required nodes. > > * One property

Re: RESEND Re: [Patch 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc

On Wed, Jun 14, 2017 at 3:25 PM, Balbir Singh wrote: > > > On Wed, Jun 14, 2017 at 8:21 AM, Michael Bringmann > wrote: >> >> On a related note, we are discussing the addition of 2 new device-tree >> properties >> with Pete Heyrman and his fellows

Re: [PATCH] powerpc64/hw_breakpoints: Handle data breakpoints in radix mode

On Wednesday 14 June 2017 10:41 AM, Naveen N. Rao wrote: Hi Aneesh, On 2017/06/14 08:38AM, Aneesh Kumar K.V wrote: "Naveen N. Rao" writes: On P9, trying to use data breakpoints throws the splat shown below (*). This is because the check for a data

Re: [PATCH] powerpc64/hw_breakpoints: Handle data breakpoints in radix mode

Hi Aneesh, On 2017/06/14 08:38AM, Aneesh Kumar K.V wrote: > "Naveen N. Rao" writes: > > > On P9, trying to use data breakpoints throws the splat shown below (*). > > This is because the check for a data breakpoint in DSISR is in > > do_hash_page(). Move this

Re: [PATCH] recordmcount.pl: Add ppc64le to list of supported architectures

On Wednesday 14 June 2017 04:22 AM, Balbir Singh wrote: On Tue, Jun 13, 2017 at 4:49 PM, Kamalesh Babulal < kamal...@linux.vnet.ibm.com> wrote: Module make on ppc64le, fails with: make -C /root/kernel/linux M=/root/.kpatch/tmp/patch kpatch-data-read-mostly.ko make[1]: Entering directory

Re: [PATCH V3] cxl: Fixes for Coherent Accelerator Interface Architecture 2.0

Christophe Lombard writes: > A previous set of patches "cxl: Add support for Coherent Accelerator > Interface Architecture 2.0" has introduced a new support for the CAPI > cards. Which commit is that? cheers > These patches have been tested on Simulation

Re: [PATCH] recordmcount.pl: Add ppc64le to list of supported architectures

Balbir Singh writes: > On Tue, Jun 13, 2017 at 4:49 PM, Kamalesh Babulal < > kamal...@linux.vnet.ibm.com> wrote: >> diff --git a/scripts/recordmcount.pl b/scripts/recordmcount.pl >> index 1633c3e..683b8b5 100755 >> --- a/scripts/recordmcount.pl >> +++

[PATCH] powernv/npu-dma.c: Remove spurious WARN_ON when a PCI device has no of_node

"4c3b89e powerpc/powernv: Add sanity checks to pnv_pci_get_{gpu|npu}_dev" introduced explicit warnings in pnv_pci_get_npu_dev() when a PCIe device has no associated device-tree node. However not all PCIe devices have an of_node and pnv_pci_get_npu_dev() gets indirectly called at least once for

Re: [PATCH] powerpc/xive: Fix offset for store EOI MMIOs

Benjamin Herrenschmidt writes: > Architecturally we should apply a 0x400 offset for these. Not doing > it will break future HW implementations. Can you elaborate a bit? You're changing a write to 0x0 to be a write to 0x400, which at face value appears like it breaks

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

On Tue, 2017-06-13 at 23:26 +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: [PATCH 0/8] Support for 24x7 hcall interface version 2

Thiago Jung Bauermann [bauer...@linux.vnet.ibm.com] wrote: > Hello, > > The hypervisor interface to access 24x7 performance counters (which collect > performance information from system power on to system power off) has been > extended in POWER9 adding new fields to the request and result element

[PATCH v2 3/3] powerpc/powernv/pci: Add support for PHB4 diagnostics

As with P7IOC and PHB3, add kernel-side support for decoding and printing diagnostic data for PHB4. Signed-off-by: Russell Currey --- No changes from v1 arch/powerpc/include/asm/opal-api.h | 75 - arch/powerpc/platforms/powernv/pci.c | 105

[PATCH v2 1/3] powerpc/powernv/pci: Reduce spam when dumping PEST

Dumping the PE State Tables (PEST) can be highly verbose if a number of PEs are affected, especially in the case where the whole PHB is frozen and 512 lines get printed. Check for duplicates when dumping the PEST to reduce useless output. For example: PE[0f8] A/B: 9726

[PATCH v2 2/3] powerpc/powernv/pci: Dynamically allocate PHB diag data

Diagnostic data for PHBs currently works by allocated a fixed-sized buffer. This is simple, but either wastes memory (though only a few kilobytes) or in the case of PHB4 isn't enough to fit the whole data blob. For machines that don't describe the diagnostic data size in the device tree, use the

Re: [PATCH 13/14] powerpc/64: runlatch CTRL[RUN] set optimisation

Benjamin Herrenschmidt writes: > On Tue, 2017-06-13 at 20:04 +1000, Michael Ellerman wrote: >> > Good idea.  Writing to CTRL register can change only the RUN field. >> > Was this any different in older generations? >> >> No AFAICS back to 2.02. >> >> > Anton and Ben

Re: [PATCH] powerpc64/hw_breakpoints: Handle data breakpoints in radix mode

"Naveen N. Rao" writes: > On P9, trying to use data breakpoints throws the splat shown below (*). > This is because the check for a data breakpoint in DSISR is in > do_hash_page(). Move this check to handle_page_fault() so as to catch > data breakpoints in both

[PATCH kernel] powerpc/debug: Add missing warn flag to WARN_ON's non-builtin path

When trapped on WARN_ON(), report_bug() is expected to return BUG_TRAP_TYPE_WARN so the caller could increment NIP by 4 and continue. The __builtin_constant_p() path of the PPC's WARN_ON() calls (indirectly) __WARN_FLAGS() which has BUGFLAG_WARNING set, however the other branch does not which

[PATCH] of: update ePAPR references to point to Devicetree Specification

From: Frank Rowand The Devicetree Specification has superseded the ePAPR as the base specification for bindings. Update files in Documentation to reference the new document. Some files are not updated because there is no hypervisor chapter in the Devicetree

Re: [PATCH] kernel/kprobes: Add test to validate pt_regs

On Fri, 9 Jun 2017 00:53:08 +0530 "Naveen N. Rao" wrote: > Add a test to verify that the registers passed in pt_regs on kprobe > (trap), optprobe (jump) and kprobe_on_ftrace (ftrace_caller) are > accurate. The tests are exercized if KPROBES_SANITY_TEST is

[PATCH] powerpc/xive: Fix offset for store EOI MMIOs

Architecturally we should apply a 0x400 offset for these. Not doing it will break future HW implementations. Signed-off-by: Benjamin Herrenschmidt --- arch/powerpc/include/asm/xive.h | 12 +++- arch/powerpc/kvm/book3s_xive_template.c | 4 ++--

Re: [PATCH 7/8] powerpc/perf/hv-24x7: Support v2 of the hypervisor API

Thiago Jung Bauermann [bauer...@linux.vnet.ibm.com] wrote: > POWER9 introduces a new version of the hypervisor API to access the 24x7 > perf counters. The new version changed some of the structures used for > requests and results. > > Signed-off-by: Thiago Jung Bauermann

Re: [PATCH] recordmcount.pl: Add ppc64le to list of supported architectures

On Tue, Jun 13, 2017 at 4:49 PM, Kamalesh Babulal < kamal...@linux.vnet.ibm.com> wrote: > Module make on ppc64le, fails with: > > make -C /root/kernel/linux M=/root/.kpatch/tmp/patch > kpatch-data-read-mostly.ko > make[1]: Entering directory '/root/kernel/linux' > CC [M]

Re: RESEND Re: [Patch 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc

On a related note, we are discussing the addition of 2 new device-tree properties with Pete Heyrman and his fellows that should simplify the determination of the set of required nodes. * One property would provide the total/max number of nodes needed by the kernel on the current hardware. * A

Re: [RFC PATCH 1/7 v1]powerpc: Free up four PTE bits to accommodate memory keys

On Tue, Jun 13, 2017 at 10:22:43AM +0530, Aneesh Kumar K.V wrote: > Ram Pai writes: > > > Rearrange PTE bits to free up bits 3, 4, 5 and 6 for > > memory keys. Bit 3, 4, 5, 6 and 57 shall be used for memory > > keys. > > > > The patch does the following change to

Re: [RFC PATCH 1/7 v1]powerpc: Free up four PTE bits to accommodate memory keys

On Tue, Jun 13, 2017 at 07:32:24AM +0530, Aneesh Kumar K.V wrote: > Ram Pai writes: > > > On Mon, Jun 12, 2017 at 12:27:44PM +0530, Aneesh Kumar K.V wrote: > >> Ram Pai writes: > >> > >> > Rearrange PTE bits to free up bits 3, 4, 5 and 6 for >

Re: WARNING: CPU: 2 PID: 7 at kernel/workqueue.c:2041 process_one_work

On Tue, May 30, 2017 at 01:24:06PM +0530, Abdul Haleem wrote: > Hi, > > Test : stress-ng > Machine : Power 8 Bare Metal > Kernel : 4.12.0-rc3 > Config : attached > gcc version: 4.8.5 > > > In file kernel/workqueue.c at line 2041 > > /* ensure we're on the correct CPU */ >

[PATCH] powerpc64/hw_breakpoints: Handle data breakpoints in radix mode

On P9, trying to use data breakpoints throws the splat shown below (*). This is because the check for a data breakpoint in DSISR is in do_hash_page(). Move this check to handle_page_fault() so as to catch data breakpoints in both hash and radix MMU modes. While at it, also remove the label '11'

[PATCH V2 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

[PATCH V2 1/2] powerpc/powernv: Get a unique token for async completions

This patch adds support to get a unique token for async completion requests. This will be used for creating non-repititive request handles for consecutive requests in OPAL-OCC command/response interface. Signed-off-by: Shilpasri G Bhat --- No changes from V1

[PATCH V2 0/2] Add support for OCC command/response interface

In P9, OCC(On Chip Controller) can be sent commands inband via shared memory based command response interface. This patch adds a platform driver to support the OCC command-response interface. The skiboot patch for the interface is posted here:

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

Hi Mark, On Tuesday 13 June 2017 05:14 PM, Mark Wielaard wrote: > I see the same on very short runs. But when doing a slightly longer run, > even just using ls -lahR, which does some more work, then I do see user > backtraces. They are still missing for some of the early samples though. > It is

[PATCH V3] cxl: Fixes for Coherent Accelerator Interface Architecture 2.0

A previous set of patches "cxl: Add support for Coherent Accelerator Interface Architecture 2.0" has introduced a new support for the CAPI cards. These patches have been tested on Simulation environment and quite a bit of them have been tested on real hardware. This patch brings new fixes after a

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

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, > > WARN_ON_ONCE is being called from idr_replace() function in file > lib/idr.c at

Re: [PATCH 13/14] powerpc/64: runlatch CTRL[RUN] set optimisation

On Tue, 2017-06-13 at 20:04 +1000, Michael Ellerman wrote: > > Good idea.  Writing to CTRL register can change only the RUN field. > > Was this any different in older generations? > > No AFAICS back to 2.02. > > > Anton and Ben kept the mfspr/mtspr part in earlier updates to this > > routine. >

Re: [PATCH] powerpc/configs: fix default values for NF_CT_PROTO_*

On Tue, 2017-06-13 at 20:49 +1000, Michael Ellerman wrote: > Davide Caratti writes: > > > NF_CT_PROTO_{SCTP,UDPLITE,DCCP} can't be set to 'm' anymore, since they > > have been redefined as 'bool': fix defconfig for linkstation, mvme5100 and > > ppc6xx platforms accordingly.

Re: [PATCH 03/13] powerpc/64s: idle process interrupts from system reset wakeup

On Tue, 13 Jun 2017 23:05:47 +1000 Nicholas Piggin wrote: > diff --git a/arch/powerpc/include/asm/hw_irq.h > b/arch/powerpc/include/asm/hw_irq.h > index f06112cf8734..8366bdc69988 100644 > --- a/arch/powerpc/include/asm/hw_irq.h > +++ b/arch/powerpc/include/asm/hw_irq.h > @@

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

Hi, On Wed, 24 May 2017 14:12:24 +0900 Masahiro Yamada yamada.masah...@socionext.com wrote: >Most of DT files in PowerPC use #include "..." to make pre-processor >include DT in the same directory, but we have 3 exceptional files >that use #include <...> for that. > >Fix them to remove

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

On Tue, 13 Jun 2017 20:21:45 +1000 Michael Ellerman m...@ellerman.id.au wrote: >Masahiro Yamada writes: ... >> Ping. >> I am not 100% sure who is responsible for this, >> but somebody, could take a look at this patch, please? > >Have you tested it actually works?

[PATCH 13/13] powerpc/64s: idle runlatch switch is done with MSR[EE]=0

2*mfmsr and 2*mtmsr can be avoided in the idle sleep/wake code because we know the MSR[EE] is clear. Acked-by: Vaidyanathan Srinivasan Signed-off-by: Nicholas Piggin --- arch/powerpc/platforms/powernv/idle.c | 12 ++-- 1 file changed, 6

[PATCH 12/13] powerpc/64: runlatch CTRL[RUN] set optimisation

The CTRL register is read-only except bit 63 which is the run latch control. This means it can be updated with a mtspr rather than mfspr/mtspr. Reviewed-by: Vaidyanathan Srinivasan Signed-off-by: Nicholas Piggin --- arch/powerpc/kernel/process.c |

[PATCH 11/13] powerpc/64s: cpuidle no memory barrier after break from idle

A memory barrier is not required after the task wakes up, only if we clear the polling flag before waking. The case where we have work to do is the important one, so optimise for it. Reviewed-by: Vaidyanathan Srinivasan Signed-off-by: Nicholas Piggin

[PATCH 10/13] powerpc/64s: cpuidle read mostly for common globals

Ensure these don't get put into bouncing cachelines. Reviewed-by: Vaidyanathan Srinivasan Reviewed-by: Gautham R. Shenoy Signed-off-by: Nicholas Piggin --- drivers/cpuidle/cpuidle-powernv.c | 10 +-

[PATCH 09/13] powerpc/64s: cpuidle set polling before enabling irqs

local_irq_enable can cause interrupts to be taken which could take significant amount of processing time. The idle process should set its polling flag before this, so another process that wakes it during this time will not have to send an IPI. Expand the TIF_POLLING_NRFLAG coverage to as large as

[PATCH 08/13] powerpc/64s: idle hmi wakeup is unlikely

In a busy system, idle wakeups can be expected from IPIs and device interrupts. Reviewed-by: Gautham R. Shenoy Signed-off-by: Nicholas Piggin --- arch/powerpc/kernel/idle_book3s.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 07/13] powerpc/64s: idle avoid SRR usage in idle sleep/wake paths

Idle code now always runs at the 0xc... effective address whether in real or virtual mode. This means rfid can be ditched, along with a lot of SRR manipulations. In the wakeup path, carry SRR1 around in r12. Use mtmsrd to change MSR states as required. This also balances the return prediction

[PATCH 06/13] powerpc/64s: idle branch to handler with virtual mode offset

Have the system reset idle wakeup handlers branched to in real mode with the 0xc... kernel address applied. This allows simplifications of avoiding rfid when switching to virtual mode in the wakeup handler. Signed-off-by: Nicholas Piggin ---

[PATCH 05/13] powerpc/64s: interrupt replay balance the return branch predictor

The __replay_interrupt code is branched to with bl, but the caller is returned to directly with rfid from the interrupt. Instead, rfid to a stub that returns to the caller with blr, which should keep the return branch predictor balanced. Reviewed-by: Gautham R. Shenoy

[PATCH 04/13] powerpc/64s: msgclr when handling doorbell exceptions

msgsnd doorbell exceptions are cleared when the doorbell interrupt is taken. However if a doorbell exception causes a system reset interrupt wake from power saving state, the message is not cleared. Processing the doorbell from the system reset interrupt requires msgclr to avoid taking the

[PATCH 03/13] powerpc/64s: idle process interrupts from system reset wakeup

When the CPU wakes from low power state, it begins at the system reset interrupt with the exception that caused the wakeup encoded in SRR1. Today, powernv idle wakeup ignores the wakeup reason (except a special case for HMI), and the regular interrupt corresponding to the exception will fire

[PATCH 02/13] powerpc/64s: idle hotplug lazy-irq simplification

Rather than concern ourselves with any soft-mask logic in the CPU hotplug handler, just hard disable interrupts. This ensures there are no lazy-irqs pending, which means we can call directly to idle instruction in order to sleep. Signed-off-by: Nicholas Piggin ---

[PATCH 01/13] powerpc/64s: idle move soft interrupt mask logic into C code

This simplifies the asm and fixes irq-off tracing over sleep instructions. Also move powersave_nap check for POWER8 into C code, and move PSSCR register value calculation for POWER9 into C. Reviewed-by: Gautham R. Shenoy Signed-off-by: Nicholas Piggin

[PATCH 00/13 v3] idle performance improvements

Since last time, I accounted for the various comments in reviews, most importantly fixed the miscalculation of SRR1 bit for the wakeup-interrupt. Verified it does the right thing and replays the right wakeup interrupt (e.g., decrementer) from __replay_interrupt stepping through the instructions in

[PATCH 00/13 v3] idle performance improvements

Since last time, I accounted for the various comments in reviews, most importantly fixed the miscalculation of SRR1 bit for the wakeup-interrupt. Verified it does the right thing and replays the right wakeup interrupt (e.g., decrementer) from __replay_interrupt stepping through the instructions in

Re: [PATCH 12/14] powerpc/64s: cpuidle no memory barrier after break from idle

On Mon, 12 Jun 2017 23:18:44 +0530 Vaidyanathan Srinivasan wrote: > * Nicholas Piggin [2017-06-12 09:58:33]: > > > A memory barrier is not required after the task wakes up, > > only if we clear the polling flag before waking. The case > > where we

Re: [PATCH 01/44] firmware/ivc: use dma_mapping_error

On Thu, Jun 08, 2017 at 03:25:26PM +0200, Christoph Hellwig wrote: > DMA_ERROR_CODE is not supposed to be used by drivers. > > Signed-off-by: Christoph Hellwig > --- > drivers/firmware/tegra/ivc.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) Acked-by: Thierry Reding

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

Hi Ravi, On Mon, 2017-06-12 at 17:28 +0530, Ravi Bangoria wrote: > So, I tested this patch along with Mark's patch[1] on elfutils an looks > like it's not working. Steps on what I did: > > After applying Mark's patch on upstream elfutils: > > $ aclocal > $ autoheader > $ autoconf > $

Re: [PATCH 13/14] powerpc/64: runlatch CTRL[RUN] set optimisation

On Tue, 13 Jun 2017 20:04:27 +1000 Michael Ellerman wrote: > Vaidyanathan Srinivasan writes: > > * Nicholas Piggin [2017-06-12 09:58:34]: > > > >> The CTRL register is read-only except bit 63 which is the run latch > >>

Re: [PATCH 06/14] powerpc/64s: interrupt replay balance the return branch predictor

On Tue, 13 Jun 2017 19:51:19 +1000 Michael Ellerman wrote: > Nicholas Piggin writes: > > > The __replay_interrupt code is branched to with bl, but the caller is > > returned to directly with rfid from the interrupt. > > > > Instead return to a return

Re: [PATCH] powerpc/configs: fix default values for NF_CT_PROTO_*

Davide Caratti writes: > NF_CT_PROTO_{SCTP,UDPLITE,DCCP} can't be set to 'm' anymore, since they > have been redefined as 'bool': fix defconfig for linkstation, mvme5100 and > ppc6xx platforms accordingly. Since when? ie. which commit changed the symbols to bool from

Re: [PATCH 08/14] powerpc/64s: idle avoid SRR usage in idle sleep/wake paths

On Tue, 13 Jun 2017 15:55:53 +0530 Gautham R Shenoy wrote: > Hi Nick, > > On Mon, Jun 12, 2017 at 09:58:29AM +1000, Nicholas Piggin wrote: > > Idle code now always runs at the 0xc... effective address whether > > in real or virtual mode. This means rfid can be ditched,

Re: RESEND Re: [Patch 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc

Michael Bringmann writes: > Here is the information from 2 different kernels. I have not been able to > retrieve > the information matching yesterday's attachments, yet, as those dumps were > acquired in April. > > Attached please find 2 dumps of similar material

Re: [PATCH 08/14] powerpc/64s: idle avoid SRR usage in idle sleep/wake paths

Hi Nick, On Mon, Jun 12, 2017 at 09:58:29AM +1000, Nicholas Piggin wrote: > Idle code now always runs at the 0xc... effective address whether > in real or virtual mode. This means rfid can be ditched, along > with a lot of SRR manipulations. > > In the wakeup path, carry SRR1 around in r12. Use

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

Masahiro Yamada writes: > Hi > > (+Anatolij Gustschin ) > > > Ping. > I am not 100% sure who is responsible for this, > but somebody, could take a look at this patch, please? Have you tested it actually works? It sounds reasonable, and if it

Re: [PATCH v2 0/6] Appended signatures support for IMA appraisal

Thiago Jung Bauermann writes: > Michael Ellerman writes: > >> Thiago Jung Bauermann writes: >> >>> On the OpenPOWER platform, secure boot and trusted boot are being >>> implemented using IMA for taking measurements

Re: [PATCH 11/16] powerpc: vio_cmo: use dev_groups and not dev_attrs for bus_type

Greg Kroah-Hartman writes: > On Fri, Jun 09, 2017 at 09:23:10PM +1000, Michael Ellerman wrote: >> Greg Kroah-Hartman writes: >> >> > On Fri, Jun 09, 2017 at 08:53:22AM +1000, Michael Ellerman wrote: >> >> Greg Kroah-Hartman

Re: [PATCH 13/14] powerpc/64: runlatch CTRL[RUN] set optimisation

Vaidyanathan Srinivasan writes: > * Nicholas Piggin [2017-06-12 09:58:34]: > >> The CTRL register is read-only except bit 63 which is the run latch >> control. This means it can be updated with a mtspr rather than >> mfspr/mtspr. >> >>

Re: [PATCH 06/14] powerpc/64s: interrupt replay balance the return branch predictor

Nicholas Piggin writes: > The __replay_interrupt code is branched to with bl, but the caller is > returned to directly with rfid from the interrupt. > > Instead return to a return stub that returns to the caller with blr, > which should do better with the return predictor. > >

Re: [kbuild-all] [PATCH] include/linux/vfio.h: Guard powerpc-specific functions with CONFIG_VFIO_SPAPR_EEH

On 06/08, Alexey Kardashevskiy wrote: >On 08/06/17 15:35, Alexey Kardashevskiy wrote: >> Hi, >> >> How did you manage to have CONFIG_EEH=y and CONFIG_VFIO_SPAPR_EEH=n? "make >> oldconfig" fixes this to CONFIG_VFIO_SPAPR_EEH=y. > > >Also, the attached config has "CONFIG_VFIO_SPAPR_EEH=m" and

[PATCH v3] net: phy: Make phy_ethtool_ksettings_get return void

Make return value void since function never return meaningfull value Signed-off-by: Yuval Shaia Acked-by: Sergei Shtylyov --- v0 ->v1: * These files were missing in v0 * drivers/net/ethernet/renesas/ravb_main.c

[PATCH] powerpc/modules: Introduce new stub code for SHN_LIVEPATCH symbols

R_PPC64_REL24 relocation type is used for a function call, where the function symbol address is resolved and stub code (a.k.a trampoline) is constructed to jump into the global entry of the function. The caller is responsible for setting up the TOC of the called function before branching and NOP

[PATCH] recordmcount.pl: Add ppc64le to list of supported architectures

Module make on ppc64le, fails with: make -C /root/kernel/linux M=/root/.kpatch/tmp/patch kpatch-data-read-mostly.ko make[1]: Entering directory '/root/kernel/linux' CC [M] /root/.kpatch/tmp/patch/patch-hook.o Arch ppc64le is not supported with CONFIG_FTRACE_MCOUNT_RECORD at

patch "powerpc: vio_cmo: use dev_groups and not dev_attrs for bus_type" added to driver-core-next

This is a note to let you know that I've just added the patch titled powerpc: vio_cmo: use dev_groups and not dev_attrs for bus_type to my driver-core git tree which can be found at git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git in the driver-core-next branch. The

patch "powerpc: vio: use dev_groups and not dev_attrs for bus_type" added to driver-core-next

This is a note to let you know that I've just added the patch titled powerpc: vio: use dev_groups and not dev_attrs for bus_type to my driver-core git tree which can be found at git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git in the driver-core-next branch. The