diff options
| author | Chenyi Qiang <chenyi.qiang@intel.com> | 2022-05-24 21:56:21 +0800 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2022-06-08 05:20:53 -0400 |
| commit | ed2351174e38ad4febbbc0dba802803e6cff8ae0 (patch) | |
| tree | dfb064b60615a54bc9cbadd60bffa5c2194a147d /arch/x86/kvm/svm/nested.c | |
| parent | 7aadaa988c5ea0894b3bbea598e4da56f078a289 (diff) | |
| download | linux-ed2351174e38ad4febbbc0dba802803e6cff8ae0.tar.gz linux-ed2351174e38ad4febbbc0dba802803e6cff8ae0.tar.bz2 linux-ed2351174e38ad4febbbc0dba802803e6cff8ae0.zip | |
KVM: x86: Extend KVM_{G,S}ET_VCPU_EVENTS to support pending triple fault
For the triple fault sythesized by KVM, e.g. the RSM path or
nested_vmx_abort(), if KVM exits to userspace before the request is
serviced, userspace could migrate the VM and lose the triple fault.
Extend KVM_{G,S}ET_VCPU_EVENTS to support pending triple fault with a
new event KVM_VCPUEVENT_VALID_FAULT_FAULT so that userspace can save and
restore the triple fault event. This extension is guarded by a new KVM
capability KVM_CAP_TRIPLE_FAULT_EVENT.
Note that in the set_vcpu_events path, userspace is able to set/clear
the triple fault request through triple_fault.pending field.
Signed-off-by: Chenyi Qiang <chenyi.qiang@intel.com>
Message-Id: <20220524135624.22988-2-chenyi.qiang@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/x86/kvm/svm/nested.c')
0 files changed, 0 insertions, 0 deletions