mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-12-04 01:24:12 +08:00
fc24d75a7f
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:
|
||
---|---|---|
.. | ||
syscalls | ||
vdso | ||
vsyscall | ||
calling.h | ||
common.c | ||
entry_32.S | ||
entry_64_compat.S | ||
entry_64.S | ||
Makefile | ||
syscall_32.c | ||
syscall_64.c | ||
thunk_32.S | ||
thunk_64.S |