diff options
| author | Nishanth Aravamudan <[email protected]> | 2014-10-18 00:50:40 +0000 |
|---|---|---|
| committer | Michael Ellerman <[email protected]> | 2014-10-28 22:41:22 +0000 |
| commit | 2c0a33f9861d38631245f7ef434ecad3413324fb (patch) | |
| tree | 3b5c5dbdd37bbd2b3ee8d1df44ce204f422a7aca /drivers/net/xen-netback/interface.c | |
| parent | powerpc/numa: use cached value of update->cpu in update_cpu_topology (diff) | |
| download | kernel-2c0a33f9861d38631245f7ef434ecad3413324fb.tar.gz kernel-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 <[email protected]>
Signed-off-by: Michael Ellerman <[email protected]>
Diffstat (limited to 'drivers/net/xen-netback/interface.c')
0 files changed, 0 insertions, 0 deletions