In some LPAR migration scenarios, device-tree modifications are
made to the affinity of the memory in the system. For instance,
it may occur that memory is installed to nodes 0,3 on a source
system, and to nodes 0,2 on a target system. Node 2 may not have
been initialized/allocated on the target
; [1.718408] 3fc20003 3bde4e34 3b80 6042 3860 3fbb0001
> > 481c 6042
> > [1.718575] 3d220003 3929f8e0 7d49502a e93d9c00 <7f8a49ae> 38a30001
> > 38800800 7ca507b4
> >
> > It turns out that we can get a pgdat in the online pgdat list where
&g
[Sorry I have only now noticed this email]
On Thu 04-08-16 16:44:10, Paul Mackerras wrote:
> It appears that commit 75ef71840539 ("mm, vmstat: add infrastructure
> for per-node vmstats", 2016-07-28) has introduced a regression on
> machines that have nodes which have no memory,
On 09/08/16 04:27, Reza Arbab wrote:
> When scanning the device tree to initialize the system NUMA topology,
> process dt elements with compatible id "ibm,hotplug-aperture" to create
> memoryless numa nodes.
>
> These nodes will be filled when hotplug occurs within the associated
> address
When scanning the device tree to initialize the system NUMA topology,
process dt elements with compatible id "ibm,hotplug-aperture" to create
memoryless numa nodes.
These nodes will be filled when hotplug occurs within the associated
address range.
Signed-off-by: Reza Arbab
It appears that commit 75ef71840539 ("mm, vmstat: add infrastructure
for per-node vmstats", 2016-07-28) has introduced a regression on
machines that have nodes which have no memory, such as the POWER8
server that I use for testing. When I boot current upstream, I get a
I was handed off a bug report about a blade not booting with a, um
newer kernel. After turning on some debugging messages, I got this
ominous message:
node 1
NODE_DATA() = c000
Which obviously comes from here:
arch/powerpc/mm/numa.c
Dave Hansen wrote:
I was handed off a bug report about a blade not booting with a, um
newer kernel.
If you're unable to provide basic information such as the kernel
version then perhaps this isn't the best forum for discussing this. :)
I'm thinking that we need to at least fix
