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>
Showing
- arch/x86/include/asm/kvm-x86-ops.h 0 additions, 1 deletionarch/x86/include/asm/kvm-x86-ops.h
- arch/x86/include/asm/kvm_host.h 0 additions, 1 deletionarch/x86/include/asm/kvm_host.h
- arch/x86/kvm/svm/svm.c 0 additions, 6 deletionsarch/x86/kvm/svm/svm.c
- arch/x86/kvm/vmx/vmx.c 0 additions, 6 deletionsarch/x86/kvm/vmx/vmx.c
- arch/x86/kvm/x86.c 1 addition, 3 deletionsarch/x86/kvm/x86.c
Loading
Please register or sign in to comment