[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <eacc2a0a-2215-4582-bf08-9c199cf23018@intel.com>
Date: Thu, 11 Sep 2025 08:20:38 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Sean Christopherson <seanjc@...gle.com>, "Xin Li (Intel)" <xin@...or.com>
Cc: linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
linux-pm@...r.kernel.org, pbonzini@...hat.com, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com, x86@...nel.org,
hpa@...or.com, rafael@...nel.org, pavel@...nel.org, brgerst@...il.com,
david.kaplan@....com, peterz@...radead.org, andrew.cooper3@...rix.com,
kprateek.nayak@....com, arjan@...ux.intel.com, chao.gao@...el.com,
rick.p.edgecombe@...el.com, dan.j.williams@...el.com
Subject: Re: [RFC PATCH v1 0/5] x86/boot, KVM: Move VMXON/VMXOFF handling from
KVM to CPU lifecycle
On 9/11/25 07:20, Sean Christopherson wrote:
> VPID and ASID allocation need to be managed system-wide, otherwise
> running KVM alongside another hypervisor-like entity will result in
> data corruption due to shared TLB state.
What other hypervisor-like entities are out there?
The TDX module needs (or will need) VMXON for some things that aren't
strictly for virtualization. But what other entities are out there?
Powered by blists - more mailing lists