diff options
author | Steven Rostedt <[email protected]> | 2012-06-07 10:21:21 -0400 |
---|---|---|
committer | Steven Rostedt <[email protected]> | 2012-06-07 10:21:21 -0400 |
commit | 7fbb98c5cb07563d3ee08714073a8e5452a96be2 (patch) | |
tree | 44eb0ef69d4de7c686d2a278c686233d61a6580b /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | c767a54ba0657e52e6edaa97cbe0b0a8bf1c1655 (diff) |
x86: Save cr2 in NMI in case NMIs take a page fault
Avi Kivity reported that page faults in NMIs could cause havic if
the NMI preempted another page fault handler:
The recent changes to NMI allow exceptions to take place in NMI
handlers, but I think that a #PF (say, due to access to vmalloc space)
is still problematic. Consider the sequence
#PF (cr2 set by processor)
NMI
...
#PF (cr2 clobbered)
do_page_fault()
IRET
...
IRET
do_page_fault()
address = read_cr2()
The last line reads the overwritten cr2 value.
Originally I wrote a patch to solve this by saving the cr2 on the stack.
Brian Gerst suggested to save it in the r12 register as both r12 and rbx
are saved by the do_nmi handler as required by the C standard. But rbx
is already used for saving if swapgs needs to be run on exit of the NMI
handler.
Link: http://lkml.kernel.org/r/[email protected]
Link: http://lkml.kernel.org/r/[email protected]
Reported-by: Avi Kivity <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: H. Peter Anvin <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Suggested-by: Brian Gerst <[email protected]>
Signed-off-by: Steven Rostedt <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions