aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/aoe
diff options
context:
space:
mode:
authorGleb Natapov <gleb@redhat.com>2010-07-08 12:41:12 +0300
committerAvi Kivity <avi@redhat.com>2010-08-02 06:40:34 +0300
commita6f177efaa5856e22ed0d3c1e81e65b41654d083 (patch)
tree440f44a7cad040393067c6aca37d2d9e013b155e /Documentation/aoe
parentedba23e51578f7cb6781461568489fc1825db4ac (diff)
downloadkernel_goldelico_gta04-a6f177efaa5856e22ed0d3c1e81e65b41654d083.zip
kernel_goldelico_gta04-a6f177efaa5856e22ed0d3c1e81e65b41654d083.tar.gz
kernel_goldelico_gta04-a6f177efaa5856e22ed0d3c1e81e65b41654d083.tar.bz2
KVM: Reenter guest after emulation failure if due to access to non-mmio address
When shadow pages are in use sometimes KVM try to emulate an instruction when it accesses a shadowed page. If emulation fails KVM un-shadows the page and reenter guest to allow vcpu to execute the instruction. If page is not in shadow page hash KVM assumes that this was attempt to do MMIO and reports emulation failure to userspace since there is no way to fix the situation. This logic has a race though. If two vcpus tries to write to the same shadowed page simultaneously both will enter emulator, but only one of them will find the page in shadow page hash since the one who founds it also removes it from there, so another cpu will report failure to userspace and will abort the guest. Fix this by checking (in addition to checking shadowed page hash) that page that caused the emulation belongs to valid memory slot. If it is then reenter the guest to allow vcpu to reexecute the instruction. Signed-off-by: Gleb Natapov <gleb@redhat.com> Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'Documentation/aoe')
0 files changed, 0 insertions, 0 deletions