summaryrefslogtreecommitdiffstats
path: root/drivers/Makefile
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2022-01-25 23:17:25 +0100
committerPaolo Bonzini <pbonzini@redhat.com>2022-01-26 18:15:04 +0100
commit4cf3d3ebe8794c449af3e0e8c1d790c97e461d20 (patch)
tree6337299fa0756707ca67565b03caee1c84e2e394 /drivers/Makefile
parentKVM: x86: Check .flags in kvm_cpuid_check_equal() too (diff)
downloadlinux-4cf3d3ebe8794c449af3e0e8c1d790c97e461d20.tar.xz
linux-4cf3d3ebe8794c449af3e0e8c1d790c97e461d20.zip
KVM: selftests: Don't skip L2's VMCALL in SMM test for SVM guest
Don't skip the vmcall() in l2_guest_code() prior to re-entering L2, doing so will result in L2 running to completion, popping '0' off the stack for RET, jumping to address '0', and ultimately dying with a triple fault shutdown. It's not at all obvious why the test re-enters L2 and re-executes VMCALL, but presumably it serves a purpose. The VMX path doesn't skip vmcall(), and the test can't possibly have passed on SVM, so just do what VMX does. Fixes: d951b2210c1a ("KVM: selftests: smm_test: Test SMM enter from L2") Cc: Maxim Levitsky <mlevitsk@redhat.com> Signed-off-by: Sean Christopherson <seanjc@google.com> Message-Id: <20220125221725.2101126-1-seanjc@google.com> Reviewed-by: Vitaly Kuznetsov <vkuznets@redhat.com> Tested-by: Vitaly Kuznetsov <vkuznets@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'drivers/Makefile')
0 files changed, 0 insertions, 0 deletions