[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <01731a9a0346b08577fad75ae560c650145c7f39.camel@intel.com>
Date: Thu, 13 Nov 2025 07:37:29 +0000
From: "Huang, Kai" <kai.huang@...el.com>
To: "Zhao, Yan Y" <yan.y.zhao@...el.com>
CC: "Du, Fan" <fan.du@...el.com>, "Li, Xiaoyao" <xiaoyao.li@...el.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>, "Hansen, Dave"
<dave.hansen@...el.com>, "david@...hat.com" <david@...hat.com>,
"thomas.lendacky@....com" <thomas.lendacky@....com>, "tabba@...gle.com"
<tabba@...gle.com>, "vbabka@...e.cz" <vbabka@...e.cz>, "kas@...nel.org"
<kas@...nel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "seanjc@...gle.com" <seanjc@...gle.com>,
"pbonzini@...hat.com" <pbonzini@...hat.com>, "binbin.wu@...ux.intel.com"
<binbin.wu@...ux.intel.com>, "ackerleytng@...gle.com"
<ackerleytng@...gle.com>, "michael.roth@....com" <michael.roth@....com>,
"Weiny, Ira" <ira.weiny@...el.com>, "Peng, Chao P" <chao.p.peng@...el.com>,
"Yamahata, Isaku" <isaku.yamahata@...el.com>, "Annapurve, Vishal"
<vannapurve@...gle.com>, "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>,
"Miao, Jun" <jun.miao@...el.com>, "x86@...nel.org" <x86@...nel.org>,
"pgonda@...gle.com" <pgonda@...gle.com>
Subject: Re: [RFC PATCH v2 03/23] x86/tdx: Enhance
tdh_phymem_page_wbinvd_hkid() to invalidate huge pages
Thanks for all the explanation.
[...]
> In [6], the new folio_page() implementation is
>
> static inline struct page *folio_page(struct folio *folio, unsigned long n)
> {
> return &folio->page + n;
> }
>
> So, invoking folio_page() should be equal to page++ in our case.
>
> [6] https://lore.kernel.org/kvm/20250901150359.867252-13-david@redhat.com
Sure. But it seems you will need to wait all patches that you mentioned to
be merged to safely use 'page++' for pages in a folio?
And if you do:
for (i = 0; i < npages; i++)
{
struct page *p = folio_page(folio, start_idx + i);
struct tdx_module_args args = {};
args.rcx = mk_keyed_paddr(hkid, p);
...
}
It should work w/o any dependency?
Anyway, I don't have any strong opinion, as long as it works. You may
choose what you want. :-)
Powered by blists - more mailing lists