powerpc/numa: ensure per-cpu NUMA mappings are correct on topology update
authorNishanth Aravamudan <nacc@linux.vnet.ibm.com>
Sat, 18 Oct 2014 00:50:40 +0000 (17:50 -0700)
committerMichael Ellerman <mpe@ellerman.id.au>
Tue, 28 Oct 2014 22:41:22 +0000 (09:41 +1100)
commit2c0a33f9861d38631245f7ef434ecad3413324fb
tree3b5c5dbdd37bbd2b3ee8d1df44ce204f422a7aca
parent49f8d8c04368d2e29cd26752715367ccafec5b1d
powerpc/numa: ensure per-cpu NUMA mappings are correct on topology update

We received a report of warning in kernel/sched/core.c where the sched
group was NULL on an LPAR after a topology update. This seems to occur
because after the topology update has moved the CPUs, cpu_to_node is
returning the old value still, which ends up breaking the consistency of
the NUMA topology in the per-cpu maps. Ensure that we update the per-cpu
fields when we re-map CPUs.

Signed-off-by: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
arch/powerpc/mm/numa.c