diff options
author | Sean Christopherson <seanjc@google.com> | 2021-12-29 02:24:37 +0300 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2022-01-19 20:12:26 +0300 |
commit | e337f7e063641ca4d040c8210d4bd790b81effb0 (patch) | |
tree | deb46d87646290d4ab9f5863cb520ae1578b02bb /virt/kvm | |
parent | fc4fad79fc3d8841562e2a85808079da5b4835f6 (diff) | |
download | linux-e337f7e063641ca4d040c8210d4bd790b81effb0.tar.xz |
KVM: selftests: Add a test to force emulation with a pending exception
Add a VMX specific test to verify that KVM doesn't explode if userspace
attempts KVM_RUN when emulation is required with a pending exception.
KVM VMX's emulation support for !unrestricted_guest punts exceptions to
userspace instead of attempting to synthesize the exception with all the
correct state (and stack switching, etc...).
Punting is acceptable as there's never been a request to support
injecting exceptions when emulating due to invalid state, but KVM has
historically assumed that userspace will do the right thing and either
clear the exception or kill the guest. Deliberately do the opposite and
attempt to re-enter the guest with a pending exception and emulation
required to verify KVM continues to punt the combination to userspace,
e.g. doesn't explode, WARN, etc...
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20211228232437.1875318-3-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'virt/kvm')
0 files changed, 0 insertions, 0 deletions