aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorNathan Fontenot <[email protected]>2018-10-29 13:43:36 -0500
committerMichael Ellerman <[email protected]>2019-01-30 23:28:56 +1100
commit81b61324922c67f73813d8a9c175f3c153f6a1c6 (patch)
tree2cb9bcb1bbe6d9d2724e2bd8f5e5aab0cbb5210a /tools/perf/scripts/python/export-to-sqlite.py
parent63da6caeb84cfad3d1e5774b7049dd1d2c9dec62 (diff)
powerpc/pseries: Perform full re-add of CPU for topology update post-migration
On pseries systems, performing a partition migration can result in altering the nodes a CPU is assigned to on the destination system. For exampl, pre-migration on the source system CPUs are in node 1 and 3, post-migration on the destination system CPUs are in nodes 2 and 3. Handling the node change for a CPU can cause corruption in the slab cache if we hit a timing where a CPUs node is changed while cache_reap() is invoked. The corruption occurs because the slab cache code appears to rely on the CPU and slab cache pages being on the same node. The current dynamic updating of a CPUs node done in arch/powerpc/mm/numa.c does not prevent us from hitting this scenario. Changing the device tree property update notification handler that recognizes an affinity change for a CPU to do a full DLPAR remove and add of the CPU instead of dynamically changing its node resolves this issue. Signed-off-by: Nathan Fontenot <[email protected]> Signed-off-by: Michael W. Bringmann <[email protected]> Tested-by: Michael W. Bringmann <[email protected]> Signed-off-by: Michael Ellerman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions