summaryrefslogtreecommitdiffstats
path: root/virt/kvm/arm
diff options
context:
space:
mode:
authorMarcelo Tosatti <mtosatti@redhat.com>2013-12-19 15:28:51 -0200
committerPaolo Bonzini <pbonzini@redhat.com>2013-12-20 19:22:49 +0100
commit989c6b34f6a9480e397b170cc62237e89bf4fdb9 (patch)
tree2c0336c3ead7c6378e0c25744df50f777bfd4098 /virt/kvm/arm
parent4c4d563b49830a66537c3f51070dad74d7a81d3a (diff)
downloadlinux-989c6b34f6a9480e397b170cc62237e89bf4fdb9.tar.gz
linux-989c6b34f6a9480e397b170cc62237e89bf4fdb9.tar.bz2
linux-989c6b34f6a9480e397b170cc62237e89bf4fdb9.zip
KVM: MMU: handle invalid root_hpa at __direct_map
It is possible for __direct_map to be called on invalid root_hpa (-1), two examples: 1) try_async_pf -> can_do_async_pf -> vmx_interrupt_allowed -> nested_vmx_vmexit 2) vmx_handle_exit -> vmx_interrupt_allowed -> nested_vmx_vmexit Then to load_vmcs12_host_state and kvm_mmu_reset_context. Check for this possibility, let fault exception be regenerated. BZ: https://bugzilla.redhat.com/show_bug.cgi?id=924916 Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'virt/kvm/arm')
0 files changed, 0 insertions, 0 deletions