On Thu, 31 Oct 2024 13:20:11 -0700, Sean Christopherson wrote:
> When getting the current VPID, e.g. to emulate a guest TLB flush, return
> vpid01 if L2 is running but with VPID disabled, i.e. if VPID is disabled
> in vmcs12. Architecturally, if VPID is disabled, then the guest and host
> effectively share VPID=0. KVM emulates this behavior by using vpid01 when
> running an L2 with VPID disabled (see prepare_vmcs02_early_rare()), and so
> KVM must also treat vpid01 as the current VPID while L2 is active.
>
> [...]
Applied to kvm-x86 fixes, thanks!
[1/1] KVM: nVMX: Treat vpid01 as current if L2 is active, but with VPID disabled
https://github.com/kvm-x86/linux/commit/2657b82a78f1
--
https://github.com/kvm-x86/linux/tree/next
