[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d119c824-4770-41d2-a926-4ab5268ea3a6@intel.com>
Date: Fri, 16 Jan 2026 14:25:35 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: Yan Zhao <yan.y.zhao@...el.com>, Ackerley Tng <ackerleytng@...gle.com>,
Vishal Annapurve <vannapurve@...gle.com>, pbonzini@...hat.com,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org, x86@...nel.org,
rick.p.edgecombe@...el.com, kas@...nel.org, tabba@...gle.com,
michael.roth@....com, david@...nel.org, sagis@...gle.com, vbabka@...e.cz,
thomas.lendacky@....com, nik.borisov@...e.com, pgonda@...gle.com,
fan.du@...el.com, jun.miao@...el.com, francescolavra.fl@...il.com,
jgross@...e.com, ira.weiny@...el.com, isaku.yamahata@...el.com,
xiaoyao.li@...el.com, kai.huang@...el.com, binbin.wu@...ux.intel.com,
chao.p.peng@...el.com, chao.gao@...el.com
Subject: Re: [PATCH v3 00/24] KVM: TDX huge page support for private memory
On 1/16/26 11:59, Sean Christopherson wrote:
> The SEAMCALL itself. I'm saying that TDH_MEM_PAGE_AUG is really just the S-EPT
> version of "make this PTE PRESENT", and that piling on sanity checks that aren't
> fundamental to TDX shouldn't be done when KVM is writing PTEs.
>
> In other words, something like this is totally fine:
>
> KVM_MMU_WARN_ON(!tdx_is_convertible_pfn(pfn));
>
> but this is not:
>
> WARN_ON_ONCE(!page_mapping(pfn_to_page(pfn)));
OK, I think I've got a better idea what you're aiming for. I think
that's totally doable going forward.
Powered by blists - more mailing lists