summaryrefslogtreecommitdiffstats
path: root/virt/kvm
diff options
context:
space:
mode:
authorAvi Kivity <avi@redhat.com>2011-02-03 15:29:52 +0200
committerMarcelo Tosatti <mtosatti@redhat.com>2011-03-17 13:08:30 -0300
commitbd3d1ec3d26b61120bb4f60b18ee99aa81839e6b (patch)
tree1da67e2ea45cad2b8460906820bf5cad15671b32 /virt/kvm
parentf86368493ec038218e8663cc1b6e5393cd8e008a (diff)
downloadlinux-bd3d1ec3d26b61120bb4f60b18ee99aa81839e6b.tar.gz
linux-bd3d1ec3d26b61120bb4f60b18ee99aa81839e6b.tar.bz2
linux-bd3d1ec3d26b61120bb4f60b18ee99aa81839e6b.zip
KVM: SVM: check for progress after IRET interception
When we enable an NMI window, we ask for an IRET intercept, since the IRET re-enables NMIs. However, the IRET intercept happens before the instruction executes, while the NMI window architecturally opens afterwards. To compensate for this mismatch, we only open the NMI window in the following exit, assuming that the IRET has by then executed; however, this assumption is not always correct; we may exit due to a host interrupt or page fault, without having executed the instruction. Fix by checking for forward progress by recording and comparing the IRET's rip. This is somewhat of a hack, since an unchaging rip does not mean that no forward progress has been made, but is the simplest fix for now. Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'virt/kvm')
0 files changed, 0 insertions, 0 deletions