diff options
| author |   Sean Christopherson <sean.j.christopherson@intel.com> | 2021-03-05 10:31:20 -0800 |
|---|---|---|
| committer |   Paolo Bonzini <pbonzini@redhat.com> | 2021-03-15 04:44:03 -0400 |
| commit | c82f1b670fd09b7aaa0856ae24d96ce0fa6230d3 (patch) | |
| tree | fd455861d0aedfce372b3ec9995e11cf3397f0cd /arch/x86/kvm/svm/nested.c | |
| parent | KVM: VMX: Don't invalidate hv_tlb_eptp if the new EPTP matches (diff) | |
| download | linux-dev-c82f1b670fd09b7aaa0856ae24d96ce0fa6230d3.tar.xz linux-dev-c82f1b670fd09b7aaa0856ae24d96ce0fa6230d3.zip | |
KVM: VMX: Explicitly check for hv_remote_flush_tlb when loading pgd
Explicitly check that kvm_x86_ops.tlb_remote_flush() points at Hyper-V's
implementation for PV flushing instead of assuming that a non-NULL
implementation means running on Hyper-V. Wrap the related logic in
ifdeffery as hv_remote_flush_tlb() is defined iff CONFIG_HYPERV!=n.
Short term, the explicit check makes it more obvious why a non-NULL
tlb_remote_flush() triggers EPTP shenanigans. Long term, this will
allow TDX to define its own implementation of tlb_remote_flush() without
running afoul of Hyper-V.
Reviewed-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20210305183123.3978098-9-seanjc@google.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