From: Tony Lindgren <tony.lindgren@linux.intel.com>
To: Xu Yilun <yilun.xu@linux.intel.com>
Cc: x86@kernel.org, linux-coco@lists.linux.dev,
linux-kernel@vger.kernel.org, Kiryl Shutsemau <kas@kernel.org>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
dave.hansen@intel.com, kvm@vger.kernel.org, yilun.xu@intel.com,
xiaoyao.li@intel.com, sohil.mehta@intel.com,
adrian.hunter@intel.com, kishen.maloor@intel.com,
peter.fang@intel.com, baolu.lu@linux.intel.com,
zhenzhong.duan@intel.com, chao.gao@intel.com,
artem.bityutskiy@linux.intel.com, nik.borisov@suse.com
Subject: Re: [PATCH v3 6/6] x86/virt/tdx: Support DPAMT when adding memory for the extensions
Date: Thu, 8 Oct 2026 08:37:12 +0300 [thread overview]
Message-ID: <ascsCPcRUBpB32DH@tlindgre-MOBL1> (raw)
In-Reply-To: <asceeI8LD5ltEOje@yilunxu-OptiPlex-7050>
On Thu, Oct 08, 2026 at 12:39:20PM +0800, Xu Yilun wrote:
> On Tue, Oct 06, 2026 at 07:36:50AM +0300, Tony Lindgren wrote:
> > On Tue, Oct 06, 2026 at 01:41:50AM +0800, Xu Yilun wrote:
> > > The TDX module uses Physical Address Metadata Table (PAMT) to track some
> > > state for each page of physical memory that it might use. 3 levels of
> > > PAMTs are used to track pages of different sizes - 1GB, 2MB and 4KB.
> > > Dynamic PAMT (DPAMT) allows saving memory by allocating 4KB PAMT
> > > dynamically, while the 1GB and 2MB levels remain allocated on TDX module
> > > initialization. The kernel has helpers to install 4K DPAMT.
> > >
> > > Although the memory for the extensions is tens of megabytes and the host
> > > allocates it in a large chunk, the TDX module accepts it at 4K
> > > granularity. Thus the host has to install 4K DPAMT for each page of it.
> > >
> > > Call tdx_pamt_get() for each page before adding it to TDX module.
> > > Normally, these operations should not fail, and if they do,
> > > intentionally keep the error handling as simple as before - leak all
> > > pages, including the installed 4K DPAMT metadata.
> > >
> > > Signed-off-by: Xu Yilun <yilun.xu@linux.intel.com>
> > > ---
> > > v3:
> > > - New patch
> > > ---
> > > arch/x86/virt/vmx/tdx/tdx.c | 9 ++++++++-
> > > 1 file changed, 8 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/arch/x86/virt/vmx/tdx/tdx.c b/arch/x86/virt/vmx/tdx/tdx.c
> > > index 5d5f9da1ab02..27a7039ee443 100644
> > > --- a/arch/x86/virt/vmx/tdx/tdx.c
> > > +++ b/arch/x86/virt/vmx/tdx/tdx.c
> > > @@ -1330,8 +1330,15 @@ static __init int tdx_ext_mem_setup(void)
> > > struct page *chunk = page + added_pages;
> > > unsigned int i;
> > >
> > > - for (i = 0; i < chunk_pages; i++)
> > > + for (i = 0; i < chunk_pages; i++) {
> > > + ret = tdx_pamt_get(page_to_pfn(chunk + i), NULL);
> > > + if (ret) {
> > > + WARN(1, "DPAMT setup error for extensions, stranded all pages\n");
> > > + goto out_free_hpa_list;
> > > + }
> > > +
> > > hpa_list->phys[i] = page_to_phys(chunk + i);
> > > + }
> > >
> > > ret = tdx_ext_mem_add(hpa_list, chunk_pages);
> > > if (ret) {
> > >
> >
> > How about just fold this change in into patch 3/6?
>
> I think patch 3/6 is already quite heavy. Is it good that I put this
> patch right after patch 3/6?
In that case you should describe that after commit XXX dynamic PAMT is
enabled and tdx_pamt_get() must be used. Otherwise it's not clear that
patch 3/6 will not work without this change.
prev parent reply other threads:[~2026-10-08 5:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 17:41 [PATCH v3 0/6] Enable TDX module extensions Xu Yilun
2026-10-05 17:41 ` [PATCH v3 1/6] x86/virt/tdx: Move TDH.SYS.CONFIG operations into a wrapper Xu Yilun
2026-10-06 23:27 ` Edgecombe, Rick P
2026-10-05 17:41 ` [PATCH v3 2/6] x86/virt/tdx: Configure add-on features on TDX module init Xu Yilun
2026-10-06 23:56 ` Edgecombe, Rick P
2026-10-08 4:18 ` Xu Yilun
2026-10-08 16:06 ` Edgecombe, Rick P
2026-10-05 17:41 ` [PATCH v3 3/6] x86/virt/tdx: Add extra memory to TDX module for the extensions Xu Yilun
2026-10-05 17:56 ` sashiko-bot
2026-10-05 17:41 ` [PATCH v3 4/6] x86/virt/tdx: Make TDX module initialize " Xu Yilun
2026-10-05 18:00 ` sashiko-bot
2026-10-08 4:25 ` Xu Yilun
2026-10-05 17:41 ` [PATCH v3 5/6] x86/virt/tdx: Re-initialize the extensions on runtime TDX module update Xu Yilun
2026-10-05 17:58 ` sashiko-bot
2026-10-08 4:47 ` Xu Yilun
2026-10-06 4:32 ` Tony Lindgren
2026-10-05 17:41 ` [PATCH v3 6/6] x86/virt/tdx: Support DPAMT when adding memory for the extensions Xu Yilun
2026-10-05 17:57 ` sashiko-bot
2026-10-08 4:31 ` Xu Yilun
2026-10-08 18:19 ` Edgecombe, Rick P
2026-10-06 4:36 ` Tony Lindgren
2026-10-08 4:39 ` Xu Yilun
2026-10-08 5:37 ` Tony Lindgren [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ascsCPcRUBpB32DH@tlindgre-MOBL1 \
--to=tony.lindgren@linux.intel.com \
--cc=adrian.hunter@intel.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=chao.gao@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kas@kernel.org \
--cc=kishen.maloor@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=nik.borisov@suse.com \
--cc=peter.fang@intel.com \
--cc=rick.p.edgecombe@intel.com \
--cc=sohil.mehta@intel.com \
--cc=x86@kernel.org \
--cc=xiaoyao.li@intel.com \
--cc=yilun.xu@intel.com \
--cc=yilun.xu@linux.intel.com \
--cc=zhenzhong.duan@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox