[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3ee65cf000465d46d0f682946c238b9310246816.camel@intel.com>
Date: Wed, 30 Jul 2025 12:59:24 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "Zhao, Yan Y" <yan.y.zhao@...el.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"seanjc@...gle.com" <seanjc@...gle.com>, "oliver.upton@...ux.dev"
<oliver.upton@...ux.dev>, "Annapurve, Vishal" <vannapurve@...gle.com>, "Li,
Xiaoyao" <xiaoyao.li@...el.com>, "kvmarm@...ts.linux.dev"
<kvmarm@...ts.linux.dev>, "Hunter, Adrian" <adrian.hunter@...el.com>,
"maz@...nel.org" <maz@...nel.org>, "pbonzini@...hat.com"
<pbonzini@...hat.com>, "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, "nik.borisov@...e.com"
<nik.borisov@...e.com>
Subject: Re: [PATCH 2/5] KVM: TDX: Exit with MEMORY_FAULT on unexpected
pending S-EPT Violation
On Wed, 2025-07-30 at 13:55 +0800, Yan Zhao wrote:
> > But hmm, tangentially related, but Yan do we have a similar problem with
> > KVM_PRE_FAULT_MEMORY after we started setting pre_fault_allowed during TD
> > finalization?
> Sean's commit 6385d01eec16 ("KVM: x86/mmu: Don't overwrite shadow-present MMU
> SPTEs when prefaulting") should have prevented repeated invocation of
> set_external_spte_present() with prefaulted entries.
Ok, great.
Powered by blists - more mailing lists