aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin/stackcollapse-record
diff options
context:
space:
mode:
authorNicholas Piggin <[email protected]>2020-11-28 17:07:22 +1000
committerMichael Ellerman <[email protected]>2020-12-04 01:01:22 +1100
commit0ce2382657f39ced2adbb927355360c3aaeb05f8 (patch)
treee1ff2a5e03a20825dc05cda911fca4795f96ea60 /tools/perf/scripts/python/bin/stackcollapse-record
parent6d247e4d264961aa3b871290f9b11a48d5a567f2 (diff)
powerpc/64s/powernv: Allow KVM to handle guest machine check details
KVM has strategies to perform machine check recovery. If a MCE hits in a guest, have the low level handler just decode and save the MCE but not try to recover anything, so KVM can deal with it. The host does not own SLBs and does not need to report the SLB state in case of a multi-hit for example, or know about the virtual memory map of the guest. UE and memory poisoning of guest pages in the host is one thing that is possibly not completely robust at the moment, but this too needs to go via KVM (possibly via the guest and back out to host via hcall) rather than being handled at a low level in the host handler. Signed-off-by: Nicholas Piggin <[email protected]> Signed-off-by: Michael Ellerman <[email protected]> Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions