linux-kernel - Re: [PATCH] KVM: nVMX: Treat vpid01 as current if L2 is active, but with VPID disabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <173078282454.2039346.17723469953189171218.b4-ty@google.com>
Date: Mon,  4 Nov 2024 21:56:00 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>, Paolo Bonzini <pbonzini@...hat.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Like Xu <like.xu.linux@...il.com>
Subject: Re: [PATCH] KVM: nVMX: Treat vpid01 as current if L2 is active, but
 with VPID disabled

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