summaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/kvm/x86_64/vmx_set_nested_state_test.c
diff options
context:
space:
mode:
authorAaron Lewis <aaronlewis () google ! com>2019-05-31 14:14:52 +0000
committerPaolo Bonzini <pbonzini@redhat.com>2019-06-19 16:11:54 +0200
commit9dba988edb31d013003b7f00e82dd56f01db70c3 (patch)
treecfcd97662a21ec345c913adabdc4dd4b4d2e86af /tools/testing/selftests/kvm/x86_64/vmx_set_nested_state_test.c
parent61cfcd545e4291d3130022e6f5f684b5d011374b (diff)
downloadlinux-9dba988edb31d013003b7f00e82dd56f01db70c3.tar.bz2
tests: kvm: Check for a kernel warning
When running with /sys/module/kvm_intel/parameters/unrestricted_guest=N, test that a kernel warning does not occur informing us that vcpu->mmio_needed=1. This can happen when KVM_RUN is called after a triple fault. This test was made to detect a bug that was reported by Syzkaller (https://groups.google.com/forum/#!topic/syzkaller/lHfau8E3SOE) and fixed with commit bbeac2830f4de ("KVM: X86: Fix residual mmio emulation request to userspace"). Signed-off-by: Aaron Lewis <aaronlewis@google.com> Reviewed-by: Jim Mattson <jmattson@google.com> Reviewed-by: Peter Shier <pshier@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/testing/selftests/kvm/x86_64/vmx_set_nested_state_test.c')
0 files changed, 0 insertions, 0 deletions