KVM: x86: return 1 unconditionally for availability of KVM_CAP_VAPIC
authorPaolo Bonzini <pbonzini@redhat.com>
Tue, 15 Feb 2022 18:16:36 +0000 (13:16 -0500)
committerPaolo Bonzini <pbonzini@redhat.com>
Fri, 18 Feb 2022 17:30:56 +0000 (12:30 -0500)
commit8a2897853c53fd3d0e381a46b194889cf6da3391
tree8b1cd3de3f8bfe05c449aa3cc1a7a13b7a8a31db
parent1e8ff29fbbde01e18d97f7b68d1e90260844ca19
KVM: x86: return 1 unconditionally for availability of KVM_CAP_VAPIC

The two ioctls used to implement userspace-accelerated TPR,
KVM_TPR_ACCESS_REPORTING and KVM_SET_VAPIC_ADDR, are available
even if hardware-accelerated TPR can be used.  So there is
no reason not to report KVM_CAP_VAPIC.

Reviewed-by: Sean Christopherson <seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
arch/x86/include/asm/kvm-x86-ops.h
arch/x86/include/asm/kvm_host.h
arch/x86/kvm/svm/svm.c
arch/x86/kvm/vmx/vmx.c
arch/x86/kvm/x86.c