Re: powerpc: Fix Text randomization

On Wed, Oct 15, 2014 at 7:38 AM, Michael Ellerman wrote: > On Fri, 2014-10-10 at 05:45:26 UTC, Vineeth Vijayan wrote: >> Right now there is no way to disable TEXT randomization on a PPC32 >> machine. text randomization happens even in the case of "echo 0 > >> /proc/sys/kernel/randomize_va_space" >

Re: [PATCH v3 25/27] Sparc/MSI: Use MSI chip framework to configure MSI/MSI-X irq

From: Yijing Wang Date: Wed, 15 Oct 2014 11:07:13 +0800 > Use MSI chip framework instead of arch MSI functions to configure > MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework. > > Signed-off-by: Yijing Wang Acked-by: David S. Miller

[PATCH v3 24/27] IA64/MSI: Use MSI chip framework to configure MSI/MSI-X irq

Use MSI chip framework instead of arch MSI functions to configure MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework. Signed-off-by: Yijing Wang --- arch/ia64/include/asm/pci.h | 10 ++ arch/ia64/kernel/msi_ia64.c | 14 ++ arch/ia64/pci/pci.c |

[PATCH v3 25/27] Sparc/MSI: Use MSI chip framework to configure MSI/MSI-X irq

Use MSI chip framework instead of arch MSI functions to configure MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework. Signed-off-by: Yijing Wang --- arch/sparc/kernel/pci.c | 14 -- arch/sparc/kernel/pci_impl.h | 12 2 files changed, 24 inserti

[PATCH v3 26/27] tile/MSI: Use MSI chip framework to configure MSI/MSI-X irq

Use MSI chip framework instead of arch MSI functions to configure MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework. Signed-off-by: Yijing Wang --- arch/tile/include/asm/pci.h | 10 ++ arch/tile/kernel/pci_gx.c | 13 +++-- 2 files changed, 21 insertions(+

[PATCH v3 27/27] PCI/MSI: Clean up unused MSI arch functions

Now we use struct msi_chip in all platforms to configure MSI/MSI-X. We can clean up the unused arch functions. Signed-off-by: Yijing Wang --- Hi Lucas, I dropped the reviewed-by, because this version has a lot changes compared to last one, I guess you may want to check it again. --- drivers/i

[PATCH v3 19/27] MIPS/Xlp/MSI: Use MSI chip framework to configure MSI/MSI-X irq

Use MSI chip framework instead of arch MSI functions to configure MSI/MSI-X IRQ. So we can manage MSI/MSI-X irq in a unified framework. Signed-off-by: Yijing Wang --- arch/mips/include/asm/netlogic/xlp-hal/pcibus.h |1 + arch/mips/pci/msi-xlp.c | 11 +-- arc

[PATCH v3 23/27] arm/iop13xx/MSI: Use MSI chip framework to configure MSI/MSI-X irq

Use MSI chip framework instead of arch MSI functions to configure MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework. Signed-off-by: Yijing Wang --- arch/arm/mach-iop13xx/include/mach/pci.h |4 arch/arm/mach-iop13xx/iq81340mc.c|3 +++ arch/arm/mach-iop13xx/

[PATCH v3 17/27] MIPS/Octeon/MSI: Use MSI chip framework to configure MSI/MSI-X irq

Use MSI chip framework instead of arch MSI functions to configure MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework. Signed-off-by: Yijing Wang --- arch/mips/include/asm/octeon/pci-octeon.h |4 +++ arch/mips/pci/msi-octeon.c| 31 --

[PATCH v3 18/27] MIPS/Xlp: Remove the dead function destroy_irq() to fix build error

Commit 465665f78a7 ("mips: Kill pointless destroy_irq()") removed the destroy_irq(). So remove the leftover one in xlp_setup_msix() to fix build error. arch/mips/pci/msi-xlp.c: In function 'xlp_setup_msix': arch/mips/pci/msi-xlp.c:447:3: error: implicit declaration of function 'destroy_irq'.. cc1

[PATCH v3 21/27] Powerpc/MSI: Use MSI chip framework to configure MSI/MSI-X irq

Use MSI chip framework instead of arch MSI functions to configure MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework. Signed-off-by: Yijing Wang --- Hi Michael, I dropped the Acked-by , because this version has a lot changes compared to last. So, I guess you may want to check

[PATCH v3 20/27] MIPS/Xlr/MSI: Use MSI chip framework to configure MSI/MSI-X irq

Use MSI chip framework instead of arch MSI functions to configure MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework. Signed-off-by: Yijing Wang --- arch/mips/pci/pci-xlr.c | 17 +++-- 1 files changed, 15 insertions(+), 2 deletions(-) diff --git a/arch/mips/pci/p

[PATCH v3 22/27] s390/MSI: Use MSI chip framework to configure MSI/MSI-X irq

Use MSI chip framework instead of arch MSI functions to configure MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework. Signed-off-by: Yijing Wang --- Hi Sebastian, I dropped the Acked-by , because this version has a lot changes compared to last. So, I guess you may want to che

[PATCH v3 16/27] Mips/MSI: Save msi chip in pci sysdata

Save msi chip in pci sysdata, add arch pci_find_msi_chip() to extract out msi chip. Signed-off-by: Yijing Wang --- arch/mips/include/asm/pci.h | 14 ++ 1 files changed, 14 insertions(+), 0 deletions(-) diff --git a/arch/mips/include/asm/pci.h b/arch/mips/include/asm/pci.h index 97

[PATCH v3 15/27] x86/MSI: Remove unused MSI weak arch functions

Now we can clean up MSI weak arch functions in x86. Signed-off-by: Yijing Wang --- arch/x86/include/asm/pci.h |5 + arch/x86/include/asm/x86_init.h |4 arch/x86/kernel/apic/io_apic.c | 21 + arch/x86/kernel/x86_init.c | 24 -

[PATCH v3 10/27] PCI/MSI: Remove useless bus->msi assignment

Now msi chip is saved in pci_sys_data in arm, we could clean the bus->msi assignment in pci core. Signed-off-by: Yijing Wang CC: Thierry Reding CC: Thomas Petazzoni --- drivers/pci/probe.c |1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/pci/probe.c b/drivers/pc

[PATCH v3 14/27] Irq_remapping/MSI: Use MSI chip framework to configure MSI/MSI-X irq

Use MSI chip framework instead of arch MSI functions to configure MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework. Signed-off-by: Yijing Wang --- drivers/iommu/irq_remapping.c | 11 --- 1 files changed, 8 insertions(+), 3 deletions(-) diff --git a/drivers/iommu/ir

[PATCH v3 00/27] Use MSI chip framework to configure MSI/MSI-X in all platforms

Now there are a lot of weak arch functions in MSI code. Thierry Reding Introduced MSI chip framework to configure MSI/MSI-X in arm, that's a better solution than overriding lots of existing weak arch functionsin. This series use MSI chip framework to refactor MSI code across all platforms to eli

[PATCH v3 11/27] PCI/MSI: Refactor struct msi_chip to make it become more common

Now there are a lot of __weak arch functions in MSI code. These functions make MSI driver complex. Thierry introduced MSI chip framework to configure MSI/MSI-X irq in arm. Use MSI chip framework to refactor all other platform MSI code to eliminate weak arch MSI functions. This patch add .restore_ir

[PATCH v3 02/27] x86/xen/MSI: Eliminate arch_msix_mask_irq() and arch_msi_mask_irq()

Commit 0e4ccb1505a9 ("PCI: Add x86_msi.msi_mask_irq() and msix_mask_irq()") introduced two __weak arch functions arch_msix_mask_irq() and arch_msi_mask_irq() to work around a bug when running xen in x86. These two functions made msi code more complex. This patch reverts the commit and introduces a

[PATCH v3 07/27] PCI: rcar: Save msi chip in pci_sys_data

Save msi chip in pci_sys_data instead of assign msi chip to every pci bus in .add_bus(). Signed-off-by: Yijing Wang --- drivers/pci/host/pcie-rcar.c | 13 +++-- 1 files changed, 3 insertions(+), 10 deletions(-) diff --git a/drivers/pci/host/pcie-rcar.c b/drivers/pci/host/pcie-rcar.c i

[PATCH v3 06/27] PCI: designware: Save msi chip in pci_sys_data

Save msi chip in pci_sys_data instead of assign msi chip to every pci bus in .add_bus(). Signed-off-by: Yijing Wang --- drivers/pci/host/pcie-designware.c | 15 --- 1 files changed, 4 insertions(+), 11 deletions(-) diff --git a/drivers/pci/host/pcie-designware.c b/drivers/pci/hos

[PATCH v3 08/27] PCI: mvebu: Save msi chip in pci_sys_data

Save msi chip in pci_sys_data instead of assign msi chip to every pci bus in .add_bus(). Signed-off-by: Yijing Wang --- drivers/pci/host/pci-mvebu.c | 10 +++--- 1 files changed, 3 insertions(+), 7 deletions(-) diff --git a/drivers/pci/host/pci-mvebu.c b/drivers/pci/host/pci-mvebu.c index

[PATCH v3 04/27] arm/MSI: Save MSI chip in pci_sys_data

Saving msi chip in pci_sys_data can make pci bus and devices don't need to know msi chip detail, it also make pci enumeration code be decoupled from msi chip. In fact, all pci devices under the same pci hostbridge share same msi chip. So msi chip should be seen as one of resources or attributes to

[PATCH v3 13/27] x86/xen/MSI: Use MSI chip framework to configure MSI/MSI-X irq

Use MSI chip framework instead of arch MSI functions to configure MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework. Signed-off-by: Yijing Wang Acked-by: David Vrabel CC: Konrad Rzeszutek Wilk --- arch/x86/pci/xen.c | 58 +++-

[PATCH v3 09/27] arm/PCI: Clean unused pcibios_add_bus() and pcibios_remove_bus()

MSI chip will be saved in pci_sys_data, now we can clean up pcibios_add_bus() and pcibios_remove_bus() in arm, and use pci_find_msi_chip() to get msi chip in core MSI code. Signed-off-by: Yijing Wang --- arch/arm/include/asm/mach/pci.h |4 arch/arm/kernel/bios32.c| 16

[PATCH v3 12/27] x86/MSI: Use MSI chip framework to configure MSI/MSI-X irq

Use MSI chip framework instead of arch MSI functions to configure MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework. Signed-off-by: Yijing Wang --- arch/x86/include/asm/pci.h | 13 + arch/x86/kernel/apic/io_apic.c | 19 +++ arch/x86/pci/acpi

[PATCH v3 01/27] MSI: Remove the redundant irq_set_chip_data()

Currently, pcie-designware, pcie-rcar and pci-tegra drivers use irq chip_data to save the msi_chip pointer. They already call irq_set_chip_data() in their own MSI irq map functions. And chip_data is an opaque pointer, how to use it is arch dependent. It should not be placed in MSI core. Signed-off

[PATCH v3 05/27] PCI: tegra: Save msi chip in pci_sys_data

Save msi chip in pci_sys_data instead of assign msi chip to every pci bus in .add_bus(). Signed-off-by: Yijing Wang --- drivers/pci/host/pci-tegra.c | 13 +++-- 1 files changed, 3 insertions(+), 10 deletions(-) diff --git a/drivers/pci/host/pci-tegra.c b/drivers/pci/host/pci-tegra.c i

[PATCH v3 03/27] s390/MSI: Use __msi_mask_irq() instead of default_msi_mask_irq()

Now only s390/MSI use default_msi_mask_irq() and default_msix_mask_irq(), replace them with the common msi mask irq functions __msi_mask_irq() and __msix_mask_irq(). Remove default_msi_mask_irq() and default_msix_mask_irq(). Signed-off-by: Yijing Wang --- arch/s390/pci/pci.c |4 ++-- include

Re: [v2] powerpc/vphn: fix endian issue in NUMA device node code

On Fri, 2014-10-10 at 08:20:33 UTC, Greg Kurz wrote: > On Tue, 7 Oct 2014 20:28:23 +1100 (EST) > Michael Ellerman wrote: > > > On Fri, 2014-03-10 at 09:13:17 UTC, Greg Kurz wrote: > > > The associativity domain numbers are obtained from the hypervisor through > > > registers and written into mem

Re: powerpc: Fix Text randomization

On Fri, 2014-10-10 at 05:45:26 UTC, Vineeth Vijayan wrote: > Right now there is no way to disable TEXT randomization on a PPC32 > machine. text randomization happens even in the case of "echo 0 > > /proc/sys/kernel/randomize_va_space" Yeah it seems to happen on ppc64 too. > This happens due to th

Re: [PATCH V2] powerpc: thp: Use tlbiel wherever possible

"Aneesh Kumar K.V" writes: > If we know that user address space has never executed on other cpus > we could use tlbiel. ping ? Can we get this merged ? > > Signed-off-by: Aneesh Kumar K.V > --- > arch/powerpc/include/asm/machdep.h| 2 +- > arch/powerpc/include/asm/tlbflush.h | 4 +- >

[PATCH v2] powerpc: Remove ppc_md.remove_memory

We have an extra level of indirection on memory hot remove which is not matched on memory hot add. Memory hotplug is book3s only, so there is no need for it. This also enables means remove_memory() (ie memory hot unplug) works on powernv. Signed-off-by: Anton Blanchard --- arch/powerpc/include/

RE: [PATCHv5] clk: ppc-corenet: rename to qoriq and add CLK_OF_DECLARE support

Hi, Scott and Mike, Could you please help review this patch. Thanks. Best Regards, Jingchang >-Original Message- >From: Jingchang Lu [mailto:jingchang...@freescale.com] >Sent: Friday, October 10, 2014 5:15 PM >To: mturque...@linaro.org >Cc: Wood Scott-B07421; linuxppc-dev@lists.ozlab

Re: [PATCH 1/4] powerpc: Dynamic DMA zone limits

On Tue, 2014-10-14 at 18:57 +1100, Benjamin Herrenschmidt wrote: > On Tue, 2014-10-14 at 09:39 +0200, Scott Wood wrote: > > For a short-term workaround, I'd rather leave CONFIG_ZONE_DMA32 where > > it > > is and put #ifdef CONFIG_FSL_SOC (with a comment) around the whole > > thing. > > I'd like to

Re: [PATCH v3 00/21] powerpc/8xx: Optimise MMU TLB handling and add support of 16k pages

On Mon, 2014-10-13 at 18:44 +0200, leroy christophe wrote: > Le 17/09/2014 22:34, Scott Wood a écrit : > > On Wed, 2014-09-17 at 22:33 +0200, christophe leroy wrote: > >> Le 17/09/2014 18:40, Scott Wood a écrit : > >>> On Wed, 2014-09-17 at 18:36 +0200, Christophe Leroy wrote: > This patchset:

[PATCH v3] rtc/tpo: Driver to support rtc and wakeup on PowerNV platform

The patch implements the OPAL rtc driver that binds with the rtc driver subsystem. The driver uses the platform device infrastructure to probe the rtc device and register it to rtc class framework. The 'wakeup' is supported depending upon the property 'has-tpo' present in the OF node. It provides a

Re: [PATCH 1/4] powerpc: Dynamic DMA zone limits

On Tue, 2014-10-14 at 09:39 +0200, Scott Wood wrote: > For a short-term workaround, I'd rather leave CONFIG_ZONE_DMA32 where > it > is and put #ifdef CONFIG_FSL_SOC (with a comment) around the whole > thing. I'd like to not enable CONFIG_ZONE_DMA32 when we don't need it, ie, on !BOOKE 64-bit Chee

[PATCH] cpuidle/powernv: Populate cpuidle state details by querying the device-tree

We hard code the metrics relevant for cpuidle states in the kernel today. Instead pick them up from the device tree so that they remain relevant and updated for the system that the kernel is running on. Cc: linux...@vger.kernel.org Cc: Rafael J. Wysocki Cc: devicet...@vger.kernel.org Cc: linuxppc

Re: [PATCH 1/4] powerpc: Dynamic DMA zone limits

On Mon, 2014-10-13 at 20:00 +1100, Michael Ellerman wrote: > On Mon, 2014-10-13 at 18:14 +1100, Anton Blanchard wrote: > > Hi Scott, > > > > > Platform code can call limit_zone_pfn() to set appropriate limits > > > for ZONE_DMA and ZONE_DMA32, and dma_direct_alloc_coherent() will > > > select a su