Re: Understanding how kernel updates MMU hash table

2012-12-10 Thread Pegasus11
Hi ben Now that many things are becoming clear let me sum up my understanding until this point. Do correct it if there are mistakes. 1. Linux page table structure (PGD, PUD, PMD and PTE) is directly used in case of architecture that lend themselves to such a tree structure for maintaining virtua

Re: [PATCH v2 1/4] kprobes/powerpc: Do not disable External interrupts during single step

2012-12-10 Thread Suzuki K. Poulose
On 12/03/2012 08:37 PM, Suzuki K. Poulose wrote: From: Suzuki K. Poulose External/Decrement exceptions have lower priority than the Debug Exception. So, we don't have to disable the External interrupts before a single step. However, on BookE, Critical Input Exception(CE) has higher priority tha

RE: [PATCH 3/4 v5] iommu/fsl: Add iommu domain attributes required by fsl PAMU driver.

2012-12-10 Thread Sethi Varun-B16395
> -Original Message- > From: Wood Scott-B07421 > Sent: Tuesday, December 11, 2012 6:31 AM > To: Sethi Varun-B16395 > Cc: Wood Scott-B07421; Joerg Roedel; linux-ker...@vger.kernel.org; > io...@lists.linux-foundation.org; linuxppc-dev@lists.ozlabs.org; Tabi > Timur-B04825 > Subject: Re: [PA

[stable] [PATCH] powerpc/ptrace: Fix build with gcc 4.6

2012-12-10 Thread Michael Neuling
From: Benjamin Herrenschmidt gcc (rightfully) complains that we are accessing beyond the end of the fpr array (we do, to access the fpscr). The only sane thing to do (whether anything in that code can be called remotely sane is debatable) is to special case fpscr and handle it as a separate stat

Re: [PATCH 5/6] powerpc: Macros for saving/restore PPR

2012-12-10 Thread Michael Ellerman
On Mon, 2012-11-26 at 17:49 -0800, Haren Myneni wrote: > On 11/22/2012 07:39 PM, Michael Neuling wrote: > > Haren Myneni wrote: > > > >> [PATCH 5/6] powerpc: Macros for saving/restore PPR > > > > Maybe we should change the names > > HTM_MEDIUM_NO_PPR => HTM_MEDIUM_PPR_DISCARD and > > HTM

Re: [PATCH 3/4 v5] iommu/fsl: Add iommu domain attributes required by fsl PAMU driver.

2012-12-10 Thread Scott Wood
On 12/10/2012 04:10:06 AM, Sethi Varun-B16395 wrote: > -Original Message- > From: Wood Scott-B07421 > Sent: Tuesday, December 04, 2012 11:53 PM > To: Sethi Varun-B16395 > Cc: Wood Scott-B07421; Joerg Roedel; linux-ker...@vger.kernel.org; > io...@lists.linux-foundation.org; linuxppc-dev@

Re: pci and pcie device-tree binding - range No cells

2012-12-10 Thread Rob Herring
On 12/10/2012 11:15 AM, Thomas Petazzoni wrote: > Dear Michal Simek, > > On Mon, 10 Dec 2012 17:05:13 +0100, Michal Simek wrote: > >> CC: Thomas: I think it will be interesting to see this discussion >> because you are using size-cell/address-cells equal 1. >> http://www.spinics.net/lists/arm-ker

Re: pci and pcie device-tree binding - range No cells

2012-12-10 Thread Mitch Bradley
On 12/10/2012 12:38 PM, Benjamin Herrenschmidt wrote: > On Mon, 2012-12-10 at 21:43 +, Grant Likely wrote: >>> Sorry for my pci ignorance (have never got hw for mb/zynq) >>> I just want to get better overview how we should we our drivers to >> be compatible. >>> >>> Does it mean that pci is sup

Re: pci and pcie device-tree binding - range No cells

2012-12-10 Thread Benjamin Herrenschmidt
On Mon, 2012-12-10 at 21:43 +, Grant Likely wrote: > > Sorry for my pci ignorance (have never got hw for mb/zynq) > > I just want to get better overview how we should we our drivers to > be compatible. > > > > Does it mean that pci is supposed be always 64 bit wide? > > And there is no option

Re: pci and pcie device-tree binding - range No cells

2012-12-10 Thread Grant Likely
On Mon, 10 Dec 2012 09:21:51 -0600, Rob Herring wrote: > On 12/10/2012 09:05 AM, Michal Simek wrote: > > On 12/10/2012 03:26 PM, Rob Herring wrote: > >> On 12/10/2012 06:20 AM, Michal Simek wrote: > >>> Hi Grant and others, > >>> > >>> I have a question regarding number of cells in ranges property

Re: pci and pcie device-tree binding - range No cells

2012-12-10 Thread Grant Likely
On Mon, 10 Dec 2012 16:37:26 +0100, Michal Simek wrote: > On 12/10/2012 04:21 PM, Rob Herring wrote: > > On 12/10/2012 09:05 AM, Michal Simek wrote: > >> On 12/10/2012 03:26 PM, Rob Herring wrote: > >>> On 12/10/2012 06:20 AM, Michal Simek wrote: > Hi Grant and others, > > I have a

Re: [RFC] Add IBM Blue Gene/Q Platform

2012-12-10 Thread Jimi Xenidis
On Dec 10, 2012, at 3:32 PM, Jimi Xenidis wrote: > > On Dec 7, 2012, at 8:31 AM, Andrew Tauferner wrote: > >> Jimi, >> Do you actually want this upstream? I assume no. >>> >>> I needed to get these long-term patches out there for the BGQ >>> community for test. >> >> To which BGQ co

Re: [RFC] Add IBM Blue Gene/Q Platform

2012-12-10 Thread Jimi Xenidis
On Dec 7, 2012, at 8:31 AM, Andrew Tauferner wrote: > Jimi, > > > > Do you actually want this upstream? I assume no. > > > > I needed to get these long-term patches out there for the BGQ > > community for test. > > To which BGQ community are you referring? This work is being done by IBM Re

Re: pci and pcie device-tree binding - range No cells

2012-12-10 Thread Thomas Petazzoni
Dear Michal Simek, On Mon, 10 Dec 2012 17:05:13 +0100, Michal Simek wrote: > CC: Thomas: I think it will be interesting to see this discussion > because you are using size-cell/address-cells equal 1. > http://www.spinics.net/lists/arm-kernel/msg211839.html Thanks for Cc'ing me. The thing is tha

Re: [PATCH v2] powerpc: fix wii_memory_fixups() compile error on 3.0.y tree

2012-12-10 Thread Ben Hutchings
On Mon, Dec 10, 2012 at 10:23:16AM -0700, Shuah Khan wrote: > Fix wii_memory_fixups() the following compile error on 3.0.y tree with > wii_defconfig on 3.0.y tree. > > CC arch/powerpc/platforms/embedded6xx/wii.o > arch/powerpc/platforms/embedded6xx/wii.c: In function ‘wii_memory_fixups’: >

[PATCH v2] powerpc: fix wii_memory_fixups() compile error on 3.0.y tree

2012-12-10 Thread Shuah Khan
Fix wii_memory_fixups() the following compile error on 3.0.y tree with wii_defconfig on 3.0.y tree. CC arch/powerpc/platforms/embedded6xx/wii.o arch/powerpc/platforms/embedded6xx/wii.c: In function ‘wii_memory_fixups’: arch/powerpc/platforms/embedded6xx/wii.c:88:2: error: format ‘%llx’ exp

Re: pci and pcie device-tree binding - range No cells

2012-12-10 Thread Michal Simek
On 12/10/2012 05:02 PM, Rob Herring wrote: On 12/10/2012 09:37 AM, Michal Simek wrote: On 12/10/2012 04:21 PM, Rob Herring wrote: On 12/10/2012 09:05 AM, Michal Simek wrote: On 12/10/2012 03:26 PM, Rob Herring wrote: On 12/10/2012 06:20 AM, Michal Simek wrote: Hi Grant and others, I have a

Re: pci and pcie device-tree binding - range No cells

2012-12-10 Thread Michal Simek
On 12/10/2012 04:52 PM, David Laight wrote: Does it mean that pci is supposed be always 64 bit wide? And there is no option to have just 32bit values. I certainly believe that all PCIe (not PCI) transfers are nominally multiples of 64bit data. And PCI? That powerpc/pci-common code was designe

Re: pci and pcie device-tree binding - range No cells

2012-12-10 Thread Rob Herring
On 12/10/2012 09:37 AM, Michal Simek wrote: > On 12/10/2012 04:21 PM, Rob Herring wrote: >> On 12/10/2012 09:05 AM, Michal Simek wrote: >>> On 12/10/2012 03:26 PM, Rob Herring wrote: On 12/10/2012 06:20 AM, Michal Simek wrote: > Hi Grant and others, > > I have a question regarding

RE: pci and pcie device-tree binding - range No cells

2012-12-10 Thread David Laight
> Does it mean that pci is supposed be always 64 bit wide? > And there is no option to have just 32bit values. I certainly believe that all PCIe (not PCI) transfers are nominally multiples of 64bit data. There are (effectively) 8 byte-lane enables to allow partial word transfers (I'm not sure whet

Re: pci and pcie device-tree binding - range No cells

2012-12-10 Thread Michal Simek
On 12/10/2012 04:21 PM, Rob Herring wrote: On 12/10/2012 09:05 AM, Michal Simek wrote: On 12/10/2012 03:26 PM, Rob Herring wrote: On 12/10/2012 06:20 AM, Michal Simek wrote: Hi Grant and others, I have a question regarding number of cells in ranges property for pci and pcie nodes. Linux pci/

Re: pci and pcie device-tree binding - range No cells

2012-12-10 Thread Rob Herring
On 12/10/2012 09:05 AM, Michal Simek wrote: > On 12/10/2012 03:26 PM, Rob Herring wrote: >> On 12/10/2012 06:20 AM, Michal Simek wrote: >>> Hi Grant and others, >>> >>> I have a question regarding number of cells in ranges property >>> for pci and pcie nodes. >>> >>> Linux pci/pcie powerpc DTSes co

Re: pci and pcie device-tree binding - range No cells

2012-12-10 Thread Michal Simek
On 12/10/2012 03:26 PM, Rob Herring wrote: On 12/10/2012 06:20 AM, Michal Simek wrote: Hi Grant and others, I have a question regarding number of cells in ranges property for pci and pcie nodes. Linux pci/pcie powerpc DTSes contain 7 cells (xpedite5370.dts, sequoia.dts, etc) but also 6 cells f

Re: pci and pcie device-tree binding - range No cells

2012-12-10 Thread Rob Herring
On 12/10/2012 06:20 AM, Michal Simek wrote: > Hi Grant and others, > > I have a question regarding number of cells in ranges property > for pci and pcie nodes. > > Linux pci/pcie powerpc DTSes contain 7 cells (xpedite5370.dts, > sequoia.dts, etc) > but also 6 cells format too (mpc832x_mds.dts) >

pci and pcie device-tree binding - range No cells

2012-12-10 Thread Michal Simek
Hi Grant and others, I have a question regarding number of cells in ranges property for pci and pcie nodes. Linux pci/pcie powerpc DTSes contain 7 cells (xpedite5370.dts, sequoia.dts, etc) but also 6 cells format too (mpc832x_mds.dts) Here is shown 6 cells ranges format and describe http://devi

Re: [PATCH v2 2/4] powerpc: Move the single step enable code to a generic path

2012-12-10 Thread Ananth N Mavinakayanahalli
On Mon, Dec 03, 2012 at 08:38:37PM +0530, Suzuki K. Poulose wrote: > From: Suzuki K. Poulose > > This patch moves the single step enable code used by kprobe to a generic > routine header so that, it can be re-used by other code, in this case, > uprobes. No functional changes. > > Signed-off-by:

RE: [PATCH 3/4 v5] iommu/fsl: Add iommu domain attributes required by fsl PAMU driver.

2012-12-10 Thread Sethi Varun-B16395
> -Original Message- > From: Wood Scott-B07421 > Sent: Tuesday, December 04, 2012 11:53 PM > To: Sethi Varun-B16395 > Cc: Wood Scott-B07421; Joerg Roedel; linux-ker...@vger.kernel.org; > io...@lists.linux-foundation.org; linuxppc-dev@lists.ozlabs.org; Tabi > Timur-B04825 > Subject: Re: [P