aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/arch/arm64/Kconfig
diff options
context:
space:
mode:
authorNishanth Aravamudan <nacc@linux.vnet.ibm.com>2014-10-17 17:50:40 -0700
committerMichael Ellerman <mpe@ellerman.id.au>2014-10-29 09:41:22 +1100
commit2c0a33f9861d38631245f7ef434ecad3413324fb (patch)
tree3b5c5dbdd37bbd2b3ee8d1df44ce204f422a7aca /arch/arm64/Kconfig
parentpowerpc/numa: use cached value of update->cpu in update_cpu_topology (diff)
downloadwireguard-linux-2c0a33f9861d38631245f7ef434ecad3413324fb.tar.xz
wireguard-linux-2c0a33f9861d38631245f7ef434ecad3413324fb.zip
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>
Diffstat (limited to 'arch/arm64/Kconfig')
0 files changed, 0 insertions, 0 deletions