aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorJan Beulich <[email protected]>2019-01-15 09:58:16 -0700
committerThomas Gleixner <[email protected]>2019-01-18 00:39:33 +0100
commitfc24d75a7f91837d7918e40719575951820b2b8f (patch)
tree08fb4bf98efdcb7a47927dc8728ad46eead86fbd /tools/perf/scripts/python/export-to-postgresql.py
parent993a110319a4a60aadbd02f6defdebe048f7773b (diff)
x86/entry/64/compat: Fix stack switching for XEN PV
While in the native case entry into the kernel happens on the trampoline stack, PV Xen kernels get entered with the current thread stack right away. Hence source and destination stacks are identical in that case, and special care is needed. Other than in sync_regs() the copying done on the INT80 path isn't NMI / #MC safe, as either of these events occurring in the middle of the stack copying would clobber data on the (source) stack. There is similar code in interrupt_entry() and nmi(), but there is no fixup required because those code paths are unreachable in XEN PV guests. [ tglx: Sanitized subject, changelog, Fixes tag and stable mail address. Sigh ] Fixes: 7f2590a110b8 ("x86/entry/64: Use a per-CPU trampoline stack for IDT entries") Signed-off-by: Jan Beulich <[email protected]> Signed-off-by: Thomas Gleixner <[email protected]> Reviewed-by: Juergen Gross <[email protected]> Acked-by: Andy Lutomirski <[email protected]> Cc: Peter Anvin <[email protected]> Cc: [email protected]> Cc: Boris Ostrovsky <[email protected]> Cc: [email protected] Link: https://lkml.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions