KVM: x86: Handle triple fault in L2 without killing L1

Browse source

Synthesize a nested VM-Exit if L2 triggers an emulated triple fault
instead of exiting to userspace, which likely will kill L1.  Any flow
that does KVM_REQ_TRIPLE_FAULT is suspect, but the most common scenario
for L2 killing L1 is if L0 (KVM) intercepts a contributory exception that
is _not_intercepted by L1.  E.g. if KVM is intercepting #GPs for the
VMware backdoor, a #GP that occurs in L2 while vectoring an injected #DF
will cause KVM to emulate triple fault.

Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Jim Mattson <jmattson@google.com>
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20210302174515.2812275-2-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

...

This commit is contained in:

Sean Christopherson 2021-03-02 09:45:14 -08:00 • committed by Paolo Bonzini

parent 6312975417

commit cb6a32c2b8

6 changed files with 50 additions and 7 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

1

arch/x86/include/asm/kvm_host.h

View file

2

arch/x86/kvm/lapic.c

View file

14

arch/x86/kvm/svm/nested.c

View file

9

arch/x86/kvm/vmx/nested.c

View file

21

arch/x86/kvm/x86.c

View file

2

arch/x86/kvm/x86.h

View file