[PATCH] fsl/usb: Add FSL USB Gadget entry in platform device id table

Add FSL USB Gadget entry in platform device id table Signed-off-by: Changming Huang Signed-off-by: Suresh Gupta --- drivers/usb/gadget/udc/fsl_udc_core.c |2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/usb/gadget/udc/fsl_udc_core.c

Re: [mm v2 0/3] Support memory cgroup hotplug

On 23/11/16 18:25, Michal Hocko wrote: > On Wed 23-11-16 15:36:51, Balbir Singh wrote: >> In the absence of hotplug we use extra memory proportional to >> (possible_nodes - online_nodes) * number_of_cgroups. PPC64 has a patch >> to disable large consumption with large number of cgroups. This

Re: [v7] QE: remove PPCisms for QE

On Wed, Sep 28, 2016 at 11:15:31AM +0800, Zhao Qiang wrote: > QE was supported on PowerPC, and dependent on PPC, > Now it is supported on other platforms. so remove PPCisms. > > Signed-off-by: Zhao Qiang > --- Changelog should be something like: soc/fsl/qe: Cleanups and

Re: [PATCH] cxl: fix coccinelle warnings

Excerpts from andrew.donnellan's message of 2016-11-23 18:06:59 +1100: > On 23/11/16 17:49, Ian Munsie wrote: > > Most of these look fine > > > >> -return debugfs_create_file(name, mode, parent, (void __force *)value, > >> _io_x64); > >> +return debugfs_create_file_unsafe(name, mode,

[PATCH v3] Fix loading of module radeonfb on PowerMac

When the linux kernel is build with (typical kernel ship with Debian installer): CONFIG_FB_OF=y CONFIG_VT_HW_CONSOLE_BINDING=y CONFIG_FB_RADEON=m The offb driver takes precedence over module radeonfb. It is then impossible to load the module, error reported is: [ 96.551486] radeonfb

Re: [mm v2 0/3] Support memory cgroup hotplug

On Wed 23-11-16 15:36:51, Balbir Singh wrote: > In the absence of hotplug we use extra memory proportional to > (possible_nodes - online_nodes) * number_of_cgroups. PPC64 has a patch > to disable large consumption with large number of cgroups. This patch > adds hotplug support to memory cgroups

RE: [PATCH V3 1/2] powerpc/mpc85xx: Update TMU device tree node for T1040/T1042

> -Original Message- > From: Scott Wood [mailto:o...@buserror.net] > Sent: Wednesday, November 23, 2016 3:07 PM > To: Troy Jia ; rui.zh...@intel.com; edubez...@gmail.com; > robh...@kernel.org; Scott Wood ; shawn...@kernel.org > Cc:

Re: [PATCH V3 1/2] powerpc/mpc85xx: Update TMU device tree node for T1040/T1042

On Tue, 2016-10-25 at 10:15 +0800, Jia Hongtao wrote: > From: Hongtao Jia > > Update #thermal-sensor-cells from 0 to 1 according to the new binding. The > sensor specifier added is the monitoring site ID, and represents the "n" in > TRITSRn and TRATSRn. > > Signed-off-by:

Re: [PATCH] cxl: fix coccinelle warnings

On 23/11/16 17:49, Ian Munsie wrote: Most of these look fine -return debugfs_create_file(name, mode, parent, (void __force *)value, _io_x64); +return debugfs_create_file_unsafe(name, mode, parent, + (void __force *)value, _io_x64); Just wondering what this one

Re: [v2,1/3] cyrus: Add poweroff/reset support

On Sun, Oct 23, 2016 at 06:48:37PM -0500, Andy Fleming wrote: > Cyrus uses GPIOs to complete board shutdown/reset. > Add nodes to indicate that support to the device tree. > > Signed-off-by: Andy Fleming > --- > v2: No changes > > arch/powerpc/boot/dts/fsl/cyrus_p5020.dts |

Re: [PATCH] cxl: fix coccinelle warnings

Most of these look fine > -return debugfs_create_file(name, mode, parent, (void __force *)value, > _io_x64); > +return debugfs_create_file_unsafe(name, mode, parent, > + (void __force *)value, _io_x64); Just wondering what this one is about? Cheers, -Ian

Re: [PATCH v2 11/11] KVM: PPC: Book3S HV: Update kvmppc_set_arch_compat() for ISA v3.00

Hi Suraj, [auto build test WARNING on next-20161122] [cannot apply to kvm-ppc/kvm-ppc-next powerpc/next kvm/linux-next v4.9-rc6 v4.9-rc5 v4.9-rc4 v4.9-rc6] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

Re: Locking API testsuite output mangled

Christian Kujau writes: > The "Locking API testsuite" output during bootup (with > CONFIG_DEBUG_LOCKING_API_SELFTESTS=y) on this PowerPC system looks > mangled, possibly related to the recent printk changes (4bcc595ccd80, > "printk: reinstate KERN_CONT for printing

[PATCH 2/2] powerpc/kvm: Corectly report KVM_CAP_PPC_ALLOC_HTAB

At present KVM on powerpc always reports KVM_CAP_PPC_ALLOC_HTAB as enabled. However, the ioctl() it advertises (KVM_PPC_ALLOCATE_HTAB) only actually works on KVM HV. On KVM PR it will fail with ENOTTY. qemu already has a workaround for this, so it's not breaking things in practice, but it would

[PATCH 1/2] kvm: Move KVM_PPC_PVINFO_FLAGS_EV_IDLE definition next to its structure

The KVM_PPC_PVINFO_FLAGS_EV_IDLE macro defines a bit for use in the flags field of struct kvm_ppc_pvinfo. However, changes since that was introduced have moved it away from that structure definition, which is confusing. Move it back next to the structure it belongs with. Signed-off-by: David

[PATCH 0/2] Preliminary cleanups for HPT resizing

Hi Paul, I'm still chasing this confusion about the CAS bit to send the real HPT resizing patches. However, in the meantime, here are some preliminary cleanups. These cleanups stand on their own, although I wrote them in the context of writing the HPT resizing code, and are prerequisites for

Re: [PATCH kernel v5 4/6] vfio/spapr: Postpone default window creation

On 23/11/16 12:35, David Gibson wrote: > On Tue, Nov 22, 2016 at 06:29:39PM +1100, Alexey Kardashevskiy wrote: >> On 22/11/16 13:50, David Gibson wrote: >>> On Fri, Nov 11, 2016 at 11:32:15PM +1100, Alexey Kardashevskiy wrote: As mentioned in the previous patch, we are going to allow the

[mm v2 3/3] powerpc/mm: fix node_possible_map limitations

We've fixed the memory hotplug issue with memcg, hence this work around should not be required. Reverts: commit 3af229f2071f ("powerpc/numa: Reset node_possible_map to only node_online_map") Cc: Tejun Heo Cc: Andrew Morton Cc: Johannes Weiner

[mm v2 2/3] mm: Move operations to hotplug callbacks

Move routines that do operations on all nodes to just the online nodes. Most of the changes are very obvious (like the ones related to soft limit tree per node) Implications of this patch 1. get/put_online_mems around for_each_online_node paths. These are expected to be !fast path 2. Memory

[mm v2 1/3] mm: Add basic infrastructure for memcg hotplug support

The lack of hotplug support makes us allocate all memory upfront for per node data structures. With large number of cgroups this can be an overhead. PPC64 actually limits n_possible nodes to n_online to avoid some of this overhead. This patch adds the basic notifiers to listen to hotplug events

[mm v2 0/3] Support memory cgroup hotplug

In the absence of hotplug we use extra memory proportional to (possible_nodes - online_nodes) * number_of_cgroups. PPC64 has a patch to disable large consumption with large number of cgroups. This patch adds hotplug support to memory cgroups and reverts the commit that limited possible nodes to

linux-next: manual merge of the kvm-ppc-paulus tree with the powerpc-fixes tree

Hi Paul, Today's linux-next merge of the kvm-ppc-paulus tree got a conflict in: arch/powerpc/include/asm/asm-prototypes.h between commit: 9e5f68842276 ("powerpc: Fix missing CRCs, add more asm-prototypes.h declarations") from the powerpc-fixes tree and commit: ebe4535fbe7a ("KVM: PPC:

Re: [PATCH RFC] powerpc/powernv: sysfs entry to force full IPL reboot

Andrew Donnellan writes: > On 23/11/16 12:37, Andrew Donnellan wrote: >>> There's existing logic in kernel/reboot.c to handle a reboot= command >>> line parameter, which can set the reboot_mode, so my preference would be >>> that we use that. >>> >>> Currently we

[PATCH] powerpc/boot: fix the early OPAL console wrappers

When configured with CONFIG_PPC_EARLY_DEBUG_OPAL=y the kernel expects the OPAL entry and base addresses to be passed in r8 and r9 respectively. Currently the wrapper does not attempt to restore these values before entering the decompressed kernel which causes the kernel to branch into whatever

Re: [PATCH v10 04/10] kexec_file: Add support for purgatory built as PIE.

Am Mittwoch, 23. November 2016, 09:32:58 BRST schrieb Dave Young: > On 11/22/16 at 11:44am, Thiago Jung Bauermann wrote: > > Am Dienstag, 22. November 2016, 17:01:10 BRST schrieb Michael Ellerman: > > > Thiago Jung Bauermann writes: > > > > Am Sonntag, 20. November

Re: [PATCH RFC] powerpc/powernv: sysfs entry to force full IPL reboot

On 23/11/16 12:37, Andrew Donnellan wrote: There's existing logic in kernel/reboot.c to handle a reboot= command line parameter, which can set the reboot_mode, so my preference would be that we use that. Currently we completely ignore the reboot_mode, so there's no backward compatibility issue.

Re: [PATCH kernel v5 5/6] vfio/spapr: Reference mm in tce_container

On Tue, Nov 22, 2016 at 06:34:25PM +1100, Alexey Kardashevskiy wrote: > On 22/11/16 14:49, Alexey Kardashevskiy wrote: > > On 22/11/16 13:38, David Gibson wrote: > >> On Thu, Nov 17, 2016 at 06:39:41PM +1100, Alexey Kardashevskiy wrote: > >>> On 11/11/16 23:32, Alexey Kardashevskiy wrote: >

Re: [PATCH kernel v5 4/6] vfio/spapr: Postpone default window creation

On Tue, Nov 22, 2016 at 06:29:39PM +1100, Alexey Kardashevskiy wrote: > On 22/11/16 13:50, David Gibson wrote: > > On Fri, Nov 11, 2016 at 11:32:15PM +1100, Alexey Kardashevskiy wrote: > >> As mentioned in the previous patch, we are going to allow the userspace > >> to configure container in one

Re: linux-next: build failure after merge of the powerpc tree

On Tue, 22 Nov 2016 21:21:14 +1100 Stephen Rothwell wrote: > Hi all, > > On Tue, 22 Nov 2016 19:58:32 +1100 Stephen Rothwell > wrote: > > > > After merging the powerpc tree, today's linux-next build (powerpc > > allyesconfig) failed like this: > >

Re: [PATCH RFC] powerpc/powernv: sysfs entry to force full IPL reboot

On 22/11/16 21:27, Michael Ellerman wrote: Can I suggest: - Fix OPAL - Fix OPAL - Fix OPAL ... Oh OK, it's firmware :D Yep :D There's existing logic in kernel/reboot.c to handle a reboot= command line parameter, which can set the reboot_mode, so my preference would be that we use that.

Re: [PATCH v10 04/10] kexec_file: Add support for purgatory built as PIE.

On 11/22/16 at 11:44am, Thiago Jung Bauermann wrote: > Am Dienstag, 22. November 2016, 17:01:10 BRST schrieb Michael Ellerman: > > Thiago Jung Bauermann writes: > > > Am Sonntag, 20. November 2016, 10:45:46 BRST schrieb Dave Young: > > >> On 11/10/16 at 01:27am,

Re: [PATCH 2/4] powerpc/64: Provide functions for accessing POWER9 partition table

Paul Mackerras writes: > On Tue, Nov 22, 2016 at 10:00:58PM +1100, Michael Ellerman wrote: >> kbuild test robot writes: >> > [auto build test WARNING on powerpc/next] >> > [cannot apply to v4.9-rc6 next-20161117] >> > [if your patch is applied to the wrong git

Re: [PATCH] powernv: Clear SPRN_PSSCR when a POWER9 CPU comes online

On Tue, 2016-11-22 at 23:36 +0530, Gautham R. Shenoy wrote: > From: "Gautham R. Shenoy" > > Ensure that PSSCR is set to a safe value corresponding to no > state-loss each time a POWER9 CPU comes online. > > Signed-off-by: Gautham R. Shenoy

[PATCH v2 11/11] KVM: PPC: Book3S HV: Update kvmppc_set_arch_compat() for ISA v3.00

From: Suraj Jitindar Singh The function kvmppc_set_arch_compat() is used to determine the value of the processor compatibility register (PCR) for a guest running in a given compatibility mode. There is currently no support for v3.00 of the ISA. Add support for v3.00 of

[PATCH v2 10/11] KVM: PPC: Book3S HV: Treat POWER9 CPU threads as independent subcores

With POWER9, each CPU thread has its own MMU context and can be in the host or a guest independently of the other threads; there is still however a restriction that all threads must use the same type of address translation, either radix tree or hashed page table (HPT). Since we only support HPT

[PATCH v2 09/11] KVM: PPC: Book3S HV: Enable hypervisor virtualization interrupts while in guest

The new XIVE interrupt controller on POWER9 can direct external interrupts to the hypervisor or the guest. The interrupts directed to the hypervisor are controlled by an LPCR bit called LPCR_HVICE, and come in as a "hypervisor virtualization interrupt". This sets the LPCR bit so that hypervisor

[PATCH v2 08/11] KVM: PPC: Book3S HV: Use stop instruction rather than nap on POWER9

POWER9 replaces the various power-saving mode instructions on POWER8 (doze, nap, sleep and rvwinkle) with a single "stop" instruction, plus a register, PSSCR, which controls the depth of the power-saving mode. This replaces the use of the nap instruction when threads are idle during guest

[PATCH v2 07/11] KVM: PPC: Book3S HV: Use OPAL XICS emulation on POWER9

POWER9 includes a new interrupt controller, called XIVE, which is quite different from the XICS interrupt controller on POWER7 and POWER8 machines. KVM-HV accesses the XICS directly in several places in order to send and clear IPIs and handle interrupts from PCI devices being passed through to

[PATCH v2 05/11] KVM: PPC: Book3S HV: Adapt TLB invalidations to work on POWER9

POWER9 adds new capabilities to the tlbie (TLB invalidate entry) and tlbiel (local tlbie) instructions. Both instructions get a set of new parameters (RIC, PRS and R) which appear as bits in the instruction word. The tlbiel instruction now has a second register operand, which contains a PID

[PATCH v2 06/11] KVM: PPC: Book3S HV: Use msgsnd for IPIs to other cores on POWER9

On POWER9, the msgsnd instruction is able to send interrupts to other cores, as well as other threads on the local core. Since msgsnd is generally simpler and faster than sending an IPI via the XICS, we use msgsnd for all IPIs sent by KVM on POWER9. Signed-off-by: Paul Mackerras

[PATCH v2 03/11] KVM: PPC: Book3S HV: Adjust host/guest context switch for POWER9

Some special-purpose registers that were present and accessible by guests on POWER8 no longer exist on POWER9, so this adds feature sections to ensure that we don't try to context-switch them when going into or out of a guest on POWER9. These are all relatively obscure, rarely-used registers, but

[PATCH v2 04/11] KVM: PPC: Book3S HV: Add new POWER9 guest-accessible SPRs

This adds code to handle two new guest-accessible special-purpose registers on POWER9: TIDR (thread ID register) and PSSCR (processor stop status and control register). They are context-switched between host and guest, and the guest values can be read and set via the one_reg interface. The PSSCR

[PATCH v2 02/11] KVM: PPC: Book3S HV: Set partition table rather than SDR1 on POWER9

On POWER9, the SDR1 register (hashed page table base address) is no longer used, and instead the hardware reads the HPT base address and size from the partition table. The partition table entry also contains the bits that specify the page size for the VRMA mapping, which were previously in the

[PATCH v2 01/11] KVM: PPC: Book3S HV: Adapt to new HPTE format on POWER9

This adapts the KVM-HV hashed page table (HPT) code to read and write HPT entries in the new format defined in Power ISA v3.00 on POWER9 machines. The new format moves the B (segment size) field from the first doubleword to the second, and trims some bits from the AVA (abbreviated virtual

[PATCH 00/11] KVM: PPC: Book3S HV: Support KVM guests on POWER9

This series of patches adds support to HV KVM for running KVM guests on POWER9 systems. This allows us to run KVM guests that use HPT (hashed page table) address translation and know about the POWER9 processor. With suitable changes to the user-mode driver, this can also run guests on POWER9 in

Locking API testsuite output mangled

The "Locking API testsuite" output during bootup (with CONFIG_DEBUG_LOCKING_API_SELFTESTS=y) on this PowerPC system looks mangled, possibly related to the recent printk changes (4bcc595ccd80, "printk: reinstate KERN_CONT for printing continuation lines"). Before (e.g. with v4.6) it looked like

Re: [PATCH] powerpc/xmon: Add support for dump in reverse

Michael Ellerman writes: > Actually I want you to rework the patch anyway :) > > Will talk tomorrow. So as discussed, lets add d1, d2, d4, d8, which dump 1/2/4/8 bytes at a time, in cpu endian, and which each value separated by space. cheers

[PATCH] powerpc/powernv: Define and set POWER9 HFSCR doorbell bit

Define and set the POWER9 HFSCR doorbell bit so that guests can use msgsndp. ISA 3.0 calls this MSGP, so name it accordingly in the code. Signed-off-by: Michael Neuling --- arch/powerpc/include/asm/reg.h| 2 ++ arch/powerpc/kernel/cpu_setup_power.S | 2 +- 2 files

Re: [PATCH] powernv: Clear SPRN_PSSCR when a POWER9 CPU comes online

On Wed, 2016-11-23 at 10:30 +1100, Michael Ellerman wrote: > "Gautham R. Shenoy" writes: > > > From: "Gautham R. Shenoy" > > > > Ensure that PSSCR is set to a safe value corresponding to no > > state-loss each time a POWER9 CPU comes online. >

Re: [PATCH] powernv: Clear SPRN_PSSCR when a POWER9 CPU comes online

"Gautham R. Shenoy" writes: > From: "Gautham R. Shenoy" > > Ensure that PSSCR is set to a safe value corresponding to no > state-loss each time a POWER9 CPU comes online. Is this a bug fix? I can't tell from the change log. cheers

Re: [PATCH v2] cpufreq, powernv: Disable preemption while checking CPU throttling state throttling state

On Tue, Nov 22, 2016 at 2:07 PM, Denis Kirjanov wrote: > With preemption turned on we can read incorrect throttling state while being > switched > to CPU on a different chip. > The following BUG_() was hit while running the 4.8-rc5 kernel compiled > with

Re: [PATCH v2 2/4] usb: dwc2: Add binding for AHB burst

On Tue, Nov 22, 2016 at 2:51 PM, Christian Lamparter wrote: > On Monday, November 21, 2016 7:32:30 PM CET John Youn wrote: >> On 11/21/2016 1:10 PM, Christian Lamparter wrote: >> > On Monday, November 21, 2016 12:16:31 PM CET John Youn wrote: >> >> On 11/18/2016 12:18 PM,

Re: [PATCH v2] powernv: Handle wakeup from idle due to SRESET

On Tue, Nov 22, 2016 at 11:06:32PM +0530, Gautham R. Shenoy wrote: > From: "Gautham R. Shenoy" > > The existing code doesn't handle the case when CPU which was in a > hardware-idle state (nap,sleep,winkle on POWER8 and various stop > states on POWER9) gets woken up due

Re: [PATCH 2/4] powerpc/64: Provide functions for accessing POWER9 partition table

On Tue, Nov 22, 2016 at 10:00:58PM +1100, Michael Ellerman wrote: > kbuild test robot writes: > > [auto build test WARNING on powerpc/next] > > [cannot apply to v4.9-rc6 next-20161117] > > [if your patch is applied to the wrong git tree, please drop us a note to > > help improve

Re: [PATCH v2 2/4] usb: dwc2: Add binding for AHB burst

On Monday, November 21, 2016 7:32:30 PM CET John Youn wrote: > On 11/21/2016 1:10 PM, Christian Lamparter wrote: > > On Monday, November 21, 2016 12:16:31 PM CET John Youn wrote: > >> On 11/18/2016 12:18 PM, Christian Lamparter wrote: > >>> On Friday, November 18, 2016 8:16:08 AM CET Rob Herring

[PATCH] powernv: Clear SPRN_PSSCR when a POWER9 CPU comes online

From: "Gautham R. Shenoy" Ensure that PSSCR is set to a safe value corresponding to no state-loss each time a POWER9 CPU comes online. Signed-off-by: Gautham R. Shenoy --- arch/powerpc/kernel/cpu_setup_power.S | 2 ++ 1 file changed, 2

Re: [PATCH 2/2] cxl: Set VPD timeout to avoid access failures

Le 21/11/2016 à 22:10, Matthew R. Ochs a écrit : Some IBM CXL devices can take up to ~120ms to complete a VPD access transaction when under heavy load. With an existing default VPD timeout of 50ms, reads/writes can fail despite there not being an issue with the underlying hardware. To avoid

[PATCH v2] powernv: Handle wakeup from idle due to SRESET

From: "Gautham R. Shenoy" The existing code doesn't handle the case when CPU which was in a hardware-idle state (nap,sleep,winkle on POWER8 and various stop states on POWER9) gets woken up due to a System Reset interrupt. This patch checks if the CPU was woken up due to

RE: [PATCH 1/2] PCI: Add pci_set_vpd_timeout() to set VPD access timeout

I had old Marvell Sky2 hardware that had slow flash. -Original Message- From: Andrew Donnellan [mailto:andrew.donnel...@au1.ibm.com] Sent: Monday, November 21, 2016 4:16 PM To: Bjorn Helgaas ; Matthew R. Ochs Cc: linux-...@vger.kernel.org;

Re: [PATCH v2] powerpc: split ftrace bits into a separate file

On Tue, 22 Nov 2016 22:04:39 +0530 "Naveen N. Rao" wrote: > entry_*.S now includes a lot more than just kernel entry/exit code. As a > first step at cleaning this up, let's split out the ftrace bits into > separate files. > > No functional changes. > >

Re: [PATCH] cxl: fix coccinelle warnings

> On Nov 22, 2016, at 4:13 AM, Andrew Donnellan > wrote: > > Fix the following coccinelle warnings: > >drivers/misc/cxl/debugfs.c:46:0-23: WARNING: fops_io_x64 should be >defined with DEFINE_DEBUGFS_ATTRIBUTE >drivers/misc/cxl/guest.c:890:5-26:

Re: [PATCH] powerpc: split ftrace bits into a separate file

On 2016/11/22 10:46AM, Steven Rostedt wrote: > On Tue, 22 Nov 2016 21:13:18 +0530 > "Naveen N. Rao" wrote: > > > Hi Steve, > > > > On 2016/11/22 09:46AM, Steven Rostedt wrote: > > > On Tue, 22 Nov 2016 15:25:32 +0530 > > > "Naveen N. Rao"

[PATCH v2] powerpc: split ftrace bits into a separate file

entry_*.S now includes a lot more than just kernel entry/exit code. As a first step at cleaning this up, let's split out the ftrace bits into separate files. No functional changes. Suggested-by: Michael Ellerman Signed-off-by: Naveen N. Rao

Re: [PATCH] powerpc: split ftrace bits into a separate file

Hi Steve, On 2016/11/22 09:46AM, Steven Rostedt wrote: > On Tue, 22 Nov 2016 15:25:32 +0530 > "Naveen N. Rao" wrote: > > > No functional changes. > > Should have a better change log though. Why did you do this? > > I'm personally fine with this, as long as the

Re: [PATCH] powerpc: split ftrace bits into a separate file

On Tue, 22 Nov 2016 21:13:18 +0530 "Naveen N. Rao" wrote: > Hi Steve, > > On 2016/11/22 09:46AM, Steven Rostedt wrote: > > On Tue, 22 Nov 2016 15:25:32 +0530 > > "Naveen N. Rao" wrote: > > > > > No functional changes. > >

Re: [PATCH] powerpc: split ftrace bits into a separate file

On Tue, 22 Nov 2016 15:25:32 +0530 "Naveen N. Rao" wrote: > No functional changes. Should have a better change log though. Why did you do this? I'm personally fine with this, as long as the powerpc maintainers are too. -- Steve > > Signed-off-by: Naveen N.

Application code deadlock observed.

Hello We have board running Linux kernel 2.6.36.4 on a Freescale/NXP PPC P4080 (QorIQ) CPU. Our 32 bit application uses real-time priority threads with the Preemptible Kernel (Low-Latency Desktop) scheduling. Toolchain we use is powerpc-linux-gcc (crosstool-NG 1.19.0) 4.4.3 in combination with

Re: [PATCH v10 04/10] kexec_file: Add support for purgatory built as PIE.

Am Dienstag, 22. November 2016, 17:01:10 BRST schrieb Michael Ellerman: > Thiago Jung Bauermann writes: > > Am Sonntag, 20. November 2016, 10:45:46 BRST schrieb Dave Young: > >> On 11/10/16 at 01:27am, Thiago Jung Bauermann wrote: > >> > powerpc's purgatory.ro has 12

[PATCH v2] cpufreq, powernv: Disable preemption while checking CPU throttling state throttling state

With preemption turned on we can read incorrect throttling state while being switched to CPU on a different chip. The following BUG_() was hit while running the 4.8-rc5 kernel compiled with CONFIG_PREEMPT_DEBUG on a POWER machine. [ 67.700897] BUG: using smp_processor_id() in preemptible

Re: [PATCH] powerpc/xmon: Fix data-breakpoint

Thanks Michael, On Tuesday 22 November 2016 05:03 PM, Michael Ellerman wrote: > Ravi Bangoria writes: > >> Xmon data-breakpoint feature is broken. >> >> Whenever there is a watchpoint match occurs, hw_breakpoint_handler will >> be called by do_break via notifier

[PATCH v2] powerpc/32: Discard ffs() function and use builtin_ffs instead

With the ffs() function as defined in arch/powerpc/include/asm/bitops.h GCC will not optimise the code in case of constant parameter, as shown by the small exemple below. int ffs_test(void) { return 4 << ffs(31); } c000b8f4 : c000b8f4: 38 00 00 01 li r0,1 c000b8f8:

Re: [PATCH] powerpc/xmon: Fix data-breakpoint

Ravi Bangoria writes: > Xmon data-breakpoint feature is broken. > > Whenever there is a watchpoint match occurs, hw_breakpoint_handler will > be called by do_break via notifier chains mechanism. If watchpoint is > registered by xmon, hw_breakpoint_handler won't

Re: [PATCH] cxl: fix coccinelle warnings

Le 22/11/2016 à 11:13, Andrew Donnellan a écrit : Fix the following coccinelle warnings: drivers/misc/cxl/debugfs.c:46:0-23: WARNING: fops_io_x64 should be defined with DEFINE_DEBUGFS_ATTRIBUTE drivers/misc/cxl/guest.c:890:5-26: WARNING: Comparison to bool

Re: [PATCH 1/2] powerpc: initial stack protector (-fstack-protector) support

Le 17/11/2016 à 12:05, Michael Ellerman a écrit : Hi Michael, I took your comments into account in v2. Shame on me, I forgot to add the list of changes from v1 to v2 in the commit log. Christophe Christophe Leroy writes: diff --git

Re: [Patch v7 0/7] microblaze/PowerPC: Move irq-xilinx to irqchip

Hi, On 11/22/2016 10:55 AM, Marc Zyngier wrote: On 14/11/16 12:13, Zubair Lutfullah Kakakhel wrote: Hi, This patch series moves the Xilinx interrupt controller driver out of arch/microblaze to drivers/irqchip and then cleans it up a bit. And then removes another implementation of the driver

Re: [PATCH 2/4] powerpc/64: Provide functions for accessing POWER9 partition table

kbuild test robot writes: > [auto build test WARNING on powerpc/next] > [cannot apply to v4.9-rc6 next-20161117] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url: >

[PATCH v2 2/2] powerpc/32: stack protector: change the canary value per task

Partially copied from commit df0698be14c66 ("ARM: stack protector: change the canary value per task") A new random value for the canary is stored in the task struct whenever a new task is forked. This is meant to allow for different canary values per task. On powerpc, GCC expects the canary

[PATCH v2 1/2] powerpc: initial stack protector (-fstack-protector) support

Partialy copied from commit c743f38013aef ("ARM: initial stack protector (-fstack-protector) support") This is the very basic stuff without the changing canary upon task switch yet. Just the Kconfig option and a constant canary value initialized at boot time. Cc: Nicolas Pitre

[PATCH v2 0/2] powerpc: stack protector (-fstack-protector) support

Add HAVE_CC_STACKPROTECTOR to powerpc. This is copied from ARM. Christophe Leroy (2): powerpc: initial stack protector (-fstack-protector) support powerpc/32: stack protector: change the canary value per task arch/powerpc/Kconfig | 1 +

Re: [Patch v7 0/7] microblaze/PowerPC: Move irq-xilinx to irqchip

On 14/11/16 12:13, Zubair Lutfullah Kakakhel wrote: > Hi, > > This patch series moves the Xilinx interrupt controller driver out > of arch/microblaze to drivers/irqchip and then cleans it up a bit. > And then removes another implementation of the driver in arch/powerpc. > > This effort results

Re: [PATCH v2 2/2] powerpc: kprobes: invoke handlers directly

On 2016/11/22 09:43PM, Michael Ellerman wrote: > "Naveen N. Rao" writes: > > On 2016/11/22 02:25PM, Masami Hiramatsu wrote: > >> On Mon, 21 Nov 2016 22:36:41 +0530 > >> "Naveen N. Rao" wrote: > >> > diff --git

Re: [PATCH v2 2/2] powerpc: kprobes: invoke handlers directly

"Naveen N. Rao" writes: > On 2016/11/22 02:25PM, Masami Hiramatsu wrote: >> On Mon, 21 Nov 2016 22:36:41 +0530 >> "Naveen N. Rao" wrote: >> > diff --git a/arch/powerpc/include/asm/kprobes.h >> >

Re: [PATCH RFC] powerpc/powernv: sysfs entry to force full IPL reboot

Andrew Donnellan writes: > skiboot now supports "fast reboot", a reboot procedure where skiboot > reinitialises hardware and loads a new kernel without re-IPLing the > machine. At present, fast reboot support is still experimental and is not > enabled by default,

Re: linux-next: build failure after merge of the powerpc tree

Hi all, On Tue, 22 Nov 2016 19:58:32 +1100 Stephen Rothwell wrote: > > After merging the powerpc tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > Inconsistent kallsyms data > Try make KALLSYMS_EXTRA_PASS=1 as a workaround > > Which is a vast

[PATCH] cxl: fix coccinelle warnings

Fix the following coccinelle warnings: drivers/misc/cxl/debugfs.c:46:0-23: WARNING: fops_io_x64 should be defined with DEFINE_DEBUGFS_ATTRIBUTE drivers/misc/cxl/guest.c:890:5-26: WARNING: Comparison to bool drivers/misc/cxl/irq.c:107:3-23: WARNING: Assignment of bool to 0/1

[PATCH] powerpc: split ftrace bits into a separate file

No functional changes. Signed-off-by: Naveen N. Rao --- arch/powerpc/kernel/Makefile| 2 + arch/powerpc/kernel/entry_32.S | 107 --- arch/powerpc/kernel/entry_64.S | 380 -- arch/powerpc/kernel/ftrace_32.S |

[PATCH] powerpc/xmon: Fix data-breakpoint

Xmon data-breakpoint feature is broken. Whenever there is a watchpoint match occurs, hw_breakpoint_handler will be called by do_break via notifier chains mechanism. If watchpoint is registered by xmon, hw_breakpoint_handler won't find any associated perf_event and returns immediately with

[PATCH RFC] powerpc/powernv: sysfs entry to force full IPL reboot

skiboot now supports "fast reboot", a reboot procedure where skiboot reinitialises hardware and loads a new kernel without re-IPLing the machine. At present, fast reboot support is still experimental and is not enabled by default, however it is intended that it will be enabled by default in a

[RFC v2] powerpc: xmon: Add address lookup for percpu symbols

Currently, in xmon, there is no obvious way to get an address for a percpu symbol for a particular cpu. Having such an ability would be good for debugging the system when percpu variables got involved. Therefore, this patch introduces a new xmon command "lp" to lookup the address for percpu

linux-next: build failure after merge of the powerpc tree

Hi all, After merging the powerpc tree, today's linux-next build (powerpc allyesconfig) failed like this: Inconsistent kallsyms data Try make KALLSYMS_EXTRA_PASS=1 as a workaround Which is a vast improvement. I'll try adding 'KALLSYMS_EXTRA_PASS=1' later and see how it goes. It would be nice

RE: fsl_pamu: erratum a007907 should be applied on all versions of E6500 chips.

Hello Scott, Do you know the IOMMU maintainer's mail address? BR Jun -Original Message- From: Scott Wood [mailto:o...@buserror.net] Sent: Tuesday, November 22, 2016 3:41 PM To: Jun Yang Cc: linuxppc-dev@lists.ozlabs.org Subject: Re: fsl_pamu: erratum a007907 should be applied on all

[PATCH v4 7/7] powerpc/mm: Batch tlb flush when invalidating pte entries

This will improve the task exit case, by batching tlb invalidates. Signed-off-by: Aneesh Kumar K.V --- arch/powerpc/include/asm/book3s/64/radix.h | 16 +++- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git

[PATCH v4 6/7] powerpc/mm: update pte_update to not do full mm tlb flush

When we are updating pte, we just need to flush the tlb mapping for that pte. Right now we do a full mm flush because we don't track page size. Update the interface to track the page size and use that to do the right tlb flush. Signed-off-by: Aneesh Kumar K.V ---

[PATCH v4 5/7] powerpc/mm/hugetlb: Switch hugetlb update to use huge_pte_update

We want to switch pte_update to use va based tlb flush. In order to do that we need to track the page size. With hugetlb we currently don't have page size available in these functions. Hence switch hugetlb to use seperate functions for update. In later patch we will update hugetlb functions to

[PATCH v4 4/7] powerpc/mm/hugetlb: Make copy of huge_ptep_get_and_clear to different platform headers

In the subsequent patch we will change the implementation of book3s 64. This also avoid #ifdef in the code. Signed-off-by: Aneesh Kumar K.V --- arch/powerpc/include/asm/book3s/32/pgtable.h | 5 + arch/powerpc/include/asm/book3s/64/hugetlb.h | 6 ++

[PATCH v4 2/7] powerpc/mm: Rename hugetlb-radix.h to hugetlb.h

We will start moving some book3s specific hugetlb functions there. Signed-off-by: Aneesh Kumar K.V --- arch/powerpc/include/asm/book3s/64/{hugetlb-radix.h => hugetlb.h} | 4 ++-- arch/powerpc/include/asm/hugetlb.h| 2 +- 2 files

[PATCH v4 3/7] powerpc/mm/hugetlb: Handle hugepage size supported by hash config

W.r.t hash page table config, we support 16MB and 16GB as the hugepage size. Update the hstate_get_psize to handle 16M and 16G. Signed-off-by: Aneesh Kumar K.V --- arch/powerpc/include/asm/book3s/64/hugetlb.h | 4 1 file changed, 4 insertions(+) diff --git

[PATCH v4 1/7] powerpc/mm: update ptep_set_access_flag to not do full mm tlb flush

When we are updating pte, we just need to flush the tlb mapping for that pte. Right now we do a full mm flush because we don't track page size. Update the interface to track the page size and use that to do the right tlb flush. Signed-off-by: Aneesh Kumar K.V ---