Re: Build regressions/improvements in v3.14-rc3

2014-02-18 Thread Geert Uytterhoeven
On Tue, Feb 18, 2014 at 10:02 AM, Geert Uytterhoeven wrote: > JFYI, when comparing v3.14-rc3[1] to v3.14-rc2[3], the summaries are: > - build errors: +17/-6 + /scratch/kisskb/src/arch/powerpc/include/asm/floppy.h: error: 'isa_bridge_pcidev' undeclared (first use in this function): => 142:20

ppc: RECLAIM_DISTANCE 10?

2014-02-18 Thread Michal Hocko
Hi, I have just noticed that ppc has RECLAIM_DISTANCE reduced to 10 set by 56608209d34b (powerpc/numa: Set a smaller value for RECLAIM_DISTANCE to enable zone reclaim). The commit message suggests that the zone reclaim is desirable for all NUMA configurations. History has shown that the zone recla

[PATCH RFC 00/31] SDHCI and SDIO IRQ improvements

2014-02-18 Thread Russell King - ARM Linux
The following patch series is targetted at two things - fixing the SDIO interrupt handling, and fixing problems with the sdhci driver. - the first two patches from Thomas Gleixner provide genirq support to allow us to fix the SDIO interrupt handling in a graceful manner. - patch 3 adds support f

[PATCH RFC 11/31] mmc: sdhci: convert generic bus width setup to library function

2014-02-18 Thread Russell King
Signed-off-by: Russell King =-DO NOT APPLY-= drivers/mmc/host/sdhci-acpi.c | 2 ++ drivers/mmc/host/sdhci-bcm-kona.c | 1 + drivers/mmc/host/sdhci-bcm2835.c | 1 + drivers/mmc/host/sdhci-cns3xxx.c | 1 + drivers/mmc/host/sdhci-dove.c | 1 + drivers/mmc/host/sdhci-esdhc-imx.c |

[PATCH RFC 12/31] mmc: sdhci: convert reset into a library function

2014-02-18 Thread Russell King
Rather than having platform_reset_enter/platform_reset_exit methods, turn the core of the reset handling into a library function which platforms can call at the appropriate moment in their (new) reset method. Signed-off-by: Russell King =-DO NOT APPLY-= drivers/mmc/host/sdhci-acpi.c | 2 ++

[PATCH RFC 19/31] mmc: sdhci: convert sdhci_set_clock() into a library function

2014-02-18 Thread Russell King
Signed-off-by: Russell King =-DO NOT APPLY-= drivers/mmc/host/sdhci-acpi.c | 2 ++ drivers/mmc/host/sdhci-bcm-kona.c | 1 + drivers/mmc/host/sdhci-bcm2835.c | 1 + drivers/mmc/host/sdhci-cns3xxx.c | 3 +-- drivers/mmc/host/sdhci-dove.c | 1 + drivers/mmc/host/sdhci-esdhc.h

[PATCH RFC 25/31] mmc: sdhci: convert sdhci_set_uhs_signaling() into a library function

2014-02-18 Thread Russell King
Add sdhci_set_uhs_signaling() and always call the set_uhs_signaling method. This avoids quirks being added into sdhci_set_uhs_signaling(). Signed-off-by: Russell King =-DO NOT APPLY-= drivers/mmc/host/sdhci-acpi.c | 2 ++ drivers/mmc/host/sdhci-bcm-kona.c | 1 + drivers/mmc/host/sdhci-b

Re: [RFC PATCH 2/3] topology: support node_numa_mem() for determining the fallback node

2014-02-18 Thread Christoph Lameter
On Mon, 17 Feb 2014, Joonsoo Kim wrote: > On Wed, Feb 12, 2014 at 04:16:11PM -0600, Christoph Lameter wrote: > > Here is another patch with some fixes. The additional logic is only > > compiled in if CONFIG_HAVE_MEMORYLESS_NODES is set. > > > > Subject: slub: Memoryless node support > > > > Suppor

Re: [RFC PATCH 2/3] topology: support node_numa_mem() for determining the fallback node

2014-02-18 Thread Christoph Lameter
On Mon, 17 Feb 2014, Joonsoo Kim wrote: > On Wed, Feb 12, 2014 at 10:51:37PM -0800, Nishanth Aravamudan wrote: > > Hi Joonsoo, > > Also, given that only ia64 and (hopefuly soon) ppc64 can set > > CONFIG_HAVE_MEMORYLESS_NODES, does that mean x86_64 can't have > > memoryless nodes present? Even with

Re: [RFC PATCH 2/3] topology: support node_numa_mem() for determining the fallback node

2014-02-18 Thread Nishanth Aravamudan
On 12.02.2014 [16:16:11 -0600], Christoph Lameter wrote: > Here is another patch with some fixes. The additional logic is only > compiled in if CONFIG_HAVE_MEMORYLESS_NODES is set. > > Subject: slub: Memoryless node support > > Support memoryless nodes by tracking which allocations are failing. >

Re: [RFC PATCH 2/3] topology: support node_numa_mem() for determining the fallback node

2014-02-18 Thread Nishanth Aravamudan
On 18.02.2014 [10:57:09 -0600], Christoph Lameter wrote: > On Mon, 17 Feb 2014, Joonsoo Kim wrote: > > > On Wed, Feb 12, 2014 at 10:51:37PM -0800, Nishanth Aravamudan wrote: > > > Hi Joonsoo, > > > Also, given that only ia64 and (hopefuly soon) ppc64 can set > > > CONFIG_HAVE_MEMORYLESS_NODES, doe

Re: [RFC PATCH 2/3] topology: support node_numa_mem() for determining the fallback node

2014-02-18 Thread Christoph Lameter
On Tue, 18 Feb 2014, Nishanth Aravamudan wrote: > > Well, on powerpc, with the hypervisor providing the resources and the > topology, you can have cpuless and memoryless nodes. I'm not sure how > "fake" the NUMA is -- as I think since the resources are virtualized to > be one system, it's logicall

Re: [RFC PATCH 2/3] topology: support node_numa_mem() for determining the fallback node

2014-02-18 Thread Nishanth Aravamudan
On 18.02.2014 [13:58:20 -0600], Christoph Lameter wrote: > On Tue, 18 Feb 2014, Nishanth Aravamudan wrote: > > > > > Well, on powerpc, with the hypervisor providing the resources and the > > topology, you can have cpuless and memoryless nodes. I'm not sure how > > "fake" the NUMA is -- as I think

Re: Anyone using SysRQ key sequences on console serial port ?

2014-02-18 Thread John Donnelly
I am enable to get one keyboard sequence responded to with the noted change in the dts . for instance: SysRQ ( Break) c Panics .. Which is a good response, and since it doesn't require a return to user mode ( I suspect ) it appears to work. Any other requests fail to report any informa

Re: [RFC PATCH 2/3] topology: support node_numa_mem() for determining the fallback node

2014-02-18 Thread Christoph Lameter
On Tue, 18 Feb 2014, Nishanth Aravamudan wrote: > We use the topology provided by the hypervisor, it does actually reflect > where CPUs and memory are, and their corresponding performance/NUMA > characteristics. And so there are actually nodes without memory that have processors? Can the hypervis

Re: [RFC PATCH 2/3] topology: support node_numa_mem() for determining the fallback node

2014-02-18 Thread Nishanth Aravamudan
On 18.02.2014 [15:49:22 -0600], Christoph Lameter wrote: > On Tue, 18 Feb 2014, Nishanth Aravamudan wrote: > > > We use the topology provided by the hypervisor, it does actually reflect > > where CPUs and memory are, and their corresponding performance/NUMA > > characteristics. > > And so there a

Re: [PATCH v3 3/3] powerpc/pseries: Report in kernel device tree update to drmgr

2014-02-18 Thread Tyrel Datwyler
On 02/16/2014 04:22 PM, Benjamin Herrenschmidt wrote: > On Fri, 2014-01-31 at 15:58 -0800, Tyrel Datwyler wrote: >> Traditionally it has been drmgr's responsibilty to update the device tree >> through the /proc/ppc64/ofdt interface after a suspend/resume operation. >> This patchset however has modi

Re: ppc: RECLAIM_DISTANCE 10?

2014-02-18 Thread Nishanth Aravamudan
Hi Michal, On 18.02.2014 [10:06:58 +0100], Michal Hocko wrote: > Hi, > I have just noticed that ppc has RECLAIM_DISTANCE reduced to 10 set by > 56608209d34b (powerpc/numa: Set a smaller value for RECLAIM_DISTANCE to > enable zone reclaim). The commit message suggests that the zone reclaim > is des

Re: [PATCH v3 3/3] powerpc/pseries: Report in kernel device tree update to drmgr

2014-02-18 Thread Benjamin Herrenschmidt
On Tue, 2014-02-18 at 15:28 -0800, Tyrel Datwyler wrote: > In this case we get a double update which I clearly neglected to > mention > in the patch. The first patch in this series actually removes an > unnecessary double update from the existing kernel implementation. The > same information is ret

Re: ppc: RECLAIM_DISTANCE 10?

2014-02-18 Thread Nishanth Aravamudan
On 18.02.2014 [15:34:05 -0800], Nishanth Aravamudan wrote: > Hi Michal, > > On 18.02.2014 [10:06:58 +0100], Michal Hocko wrote: > > Hi, > > I have just noticed that ppc has RECLAIM_DISTANCE reduced to 10 set by > > 56608209d34b (powerpc/numa: Set a smaller value for RECLAIM_DISTANCE to > > enable

Re: [PATCH][v2] powerpc/fsl: Add/update miscellaneous missing bindings

2014-02-18 Thread Scott Wood
On Thu, 2014-02-13 at 12:59 +0530, Harninder Rai wrote: > Missing bindings were found on running checkpatch.pl on bsc9132 > device tree. This patch add/update the following > > - Add bindings for L2 cache controller > - Add bindings for memory controller > - Update bindings for USB controller > >

Re: ppc: RECLAIM_DISTANCE 10?

2014-02-18 Thread Nishanth Aravamudan
On 18.02.2014 [15:58:00 -0800], Nishanth Aravamudan wrote: > On 18.02.2014 [15:34:05 -0800], Nishanth Aravamudan wrote: > > Hi Michal, > > > > On 18.02.2014 [10:06:58 +0100], Michal Hocko wrote: > > > Hi, > > > I have just noticed that ppc has RECLAIM_DISTANCE reduced to 10 set by > > > 56608209d3