On Tue, Feb 18, 2014 at 10:02 AM, Geert Uytterhoeven
ge...@linux-m68k.org 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
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
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
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
=-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 +
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 rmk+ker...@arm.linux.org.uk
=-DO NOT APPLY-=
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
=-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 +
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 rmk+ker...@arm.linux.org.uk
=-DO NOT APPLY-=
drivers/mmc/host/sdhci-acpi.c | 2 ++
drivers/mmc/host/sdhci-bcm-kona.c | 1
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
Support memoryless
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
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.
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, does that mean
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 logically
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 since the
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
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 hypervisor
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 are
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 modified
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
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
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 zone
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
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
56608209d34b
22 matches
Mail list logo
