From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "yilun.xu@linux.intel.com" <yilun.xu@linux.intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"Li, Xiaoyao" <xiaoyao.li@intel.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"baolu.lu@linux.intel.com" <baolu.lu@linux.intel.com>,
"Hunter, Adrian" <adrian.hunter@intel.com>,
"tony.lindgren@linux.intel.com" <tony.lindgren@linux.intel.com>,
"kas@kernel.org" <kas@kernel.org>,
"artem.bityutskiy@linux.intel.com"
<artem.bityutskiy@linux.intel.com>,
"Xu, Yilun" <yilun.xu@intel.com>,
"nik.borisov@suse.com" <nik.borisov@suse.com>,
"Mehta, Sohil" <sohil.mehta@intel.com>,
"Duan, Zhenzhong" <zhenzhong.duan@intel.com>,
"Gao, Chao" <chao.gao@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Fang, Peter" <peter.fang@intel.com>,
"Maloor, Kishen" <kishen.maloor@intel.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH v3 4/6] x86/virt/tdx: Make TDX module initialize the extensions
Date: Mon, 12 Oct 2026 16:10:04 +0000 [thread overview]
Message-ID: <427a04b25fe2bc754a261c0b415f04d04bc04481.camel@intel.com> (raw)
In-Reply-To: <aspuIg3Oeaw1LWZ1@yilunxu-OptiPlex-7050>
On Sun, 2026-10-11 at 00:56 +0800, Xu Yilun wrote:
> Good to me. I re-wrote a new version:
>
> TDX module extensions use kernel-gifted memory for their execution
> environment to serve SEAMCALL leafs. Several add-on features depend on
> the extensions to execute their SEAMCALL leafs.
>
> After providing all required memory to the TDX module, initialize TDX
> module extensions via TDH.EXT.INIT. This is a time-consuming process,
> during which the TDX module loads its internal extension image into this
> memory and builds the execution environment. Once initialized, those
> add-on features can use their SEAMCALL leafs normally.
Looks good. But I'd still wonder how "time consuming". Should we say on the
order of booting a tiny VM? Maybe we don't know and that^ is the best we can do.
next prev parent reply other threads:[~2026-10-12 16:10 UTC|newest]
Thread overview: 39+ 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-09 13:08 ` Kiryl Shutsemau
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-09 13:14 ` Kiryl Shutsemau
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-10 2:36 ` Xu Yilun
2026-10-09 18:58 ` Edgecombe, Rick P
2026-10-10 3:20 ` Xu Yilun
2026-10-12 22:42 ` Edgecombe, Rick P
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-09 13:32 ` Kiryl Shutsemau
2026-10-09 19:03 ` Edgecombe, Rick P
2026-10-10 16:56 ` Xu Yilun
2026-10-12 16:10 ` Edgecombe, Rick P [this message]
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-09 13:34 ` Kiryl Shutsemau
2026-10-09 19:20 ` Edgecombe, Rick P
2026-10-13 10:12 ` Xu Yilun
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
2026-10-09 13:28 ` Kiryl Shutsemau
2026-10-10 3:38 ` Xu Yilun
2026-10-12 10:15 ` Kiryl Shutsemau
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=427a04b25fe2bc754a261c0b415f04d04bc04481.camel@intel.com \
--to=rick.p.edgecombe@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=sohil.mehta@intel.com \
--cc=tony.lindgren@linux.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