@@ -1152,7 +1152,7 @@ The following bits are defined in the flags field:
- KVM_VCPUEVENT_VALID_TRIPLE_FAULT may be set to signal that the
triple_fault_pending field contains a valid state. This bit will
- be set whenever KVM_CAP_TRIPLE_FAULT_EVENT is enabled.
+ be set whenever KVM_CAP_X86_TRIPLE_FAULT_EVENT is enabled.
ARM64:
^^^^^^
@@ -1249,7 +1249,7 @@ can be set in the flags field to signal that the
exception_has_payload, exception_payload, and exception.pending fields
contain a valid state and shall be written into the VCPU.
-If KVM_CAP_TRIPLE_FAULT_EVENT is enabled, KVM_VCPUEVENT_VALID_TRIPLE_FAULT
+If KVM_CAP_X86_TRIPLE_FAULT_EVENT is enabled, KVM_VCPUEVENT_VALID_TRIPLE_FAULT
can be set in flags field to signal that the triple_fault field contains
a valid state and shall be written into the VCPU.
@@ -47,7 +47,7 @@ int main(void)
struct ucall uc;
struct kvm_enable_cap cap = {
- .cap = KVM_CAP_TRIPLE_FAULT_EVENT,
+ .cap = KVM_CAP_X86_TRIPLE_FAULT_EVENT,
.args = {1}
};
@@ -56,8 +56,8 @@ int main(void)
exit(KSFT_SKIP);
}
- if (!kvm_check_cap(KVM_CAP_TRIPLE_FAULT_EVENT)) {
- print_skip("KVM_CAP_TRIPLE_FAULT_EVENT not supported");
+ if (!kvm_check_cap(KVM_CAP_X86_TRIPLE_FAULT_EVENT)) {
+ print_skip("KVM_CAP_X86_TRIPLE_FAULT_EVENT not supported");
exit(KSFT_SKIP);
}
The x86-only KVM_CAP_TRIPLE_FAULT_EVENT was (appropriately) renamed to KVM_CAP_X86_TRIPLE_FAULT_EVENT when the patches were applied, but the docs and selftests got left behind. Fix them. Signed-off-by: Sean Christopherson <seanjc@google.com> --- Documentation/virt/kvm/api.rst | 4 ++-- .../testing/selftests/kvm/x86_64/triple_fault_event_test.c | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-)