From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Gao, Chao" <chao.gao@intel.com>
Cc: "Van De Ven, Arjan" <arjan.van.de.ven@intel.com>,
"Xu, Yilun" <yilun.xu@intel.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"kas@kernel.org" <kas@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>,
"tglx@kernel.org" <tglx@kernel.org>
Subject: Re: [RFC PATCH v2 2/2] x86/virt/seamldr: Support multiple sigstruct pages
Date: Mon, 9 Nov 2026 22:12:32 +0000 [thread overview]
Message-ID: <91506ebc258a9db8b2aa47310a03b60e3c653314.camel@intel.com> (raw)
In-Reply-To: <20261106132159.1551365-3-chao.gao@intel.com>
On Fri, 2026-11-06 at 05:21 -0800, Chao Gao wrote:
> Each TDX module update image carries a sigstruct, which is passed along
> with the module binary to P-SEAMLDR. 'struct seamldr_params' has a single
> physical address slot for it, so a sigstruct can be at most one 4KB page.
"it" could refer to the module binary or the sigstruct, until you piece it
together at the end. Also struct seamldr_params could be introduced. To answer:
Is it the TDX module ABI? Or the kernels internal struct?
>
> TDX modules are moving to a post-quantum signature algorithm. Its
> signatures are far larger than the ones in use today, so the sigstruct
> no longer fits in 4KB.
>
> The P-SEAMLDR ABI was extended for this. It now has four sigstruct
> address slots instead of one, for sigstructs of up to 16KB. A new
> 'version' value of 1 tells P-SEAMLDR that this layout is in use.
>
> Extend 'struct seamldr_params' to match the new ABI. The sigstruct
> address list is already populated in a loop over all sigstruct pages, so
> raising SEAMLDR_MAX_NR_SIG_PAGES is enough to fill the new slots
Missing period. Also, the existing loop is a bit strange. I wonder if it needs
to be explained, but the explanation is probably that it was not adapted
properly after this change was removed from the original series.
>
> Set 'version' to 1 only when the sigstruct spans more than one page. Old
> P-SEAMLDRs reject version 1, so this keeps updates with a single-page
> sigstruct working on them.
>
> Do not query P-SEAMLDR for version 1 support. Userspace selects the
> update image and is responsible for ensuring the module is compatible
> with P-SEAMLDR.
>
> AI was used under supervision to review code and workshop logs
Missing period. But this phrase is starting to become kind of boiler plate in
all of these patches. I wonder if it's still needed. AI review is now the
exception. Maybe move it below the "---" for this time? Dave can move it up
easily if he thinks it helps.
>
> Signed-off-by: Chao Gao <chao.gao@intel.com>
> ---
Otherwise lgtm.
> v2:
> - drop macros for versions to keep the diff minimal
> - explain why the sigstruct filling code needs no change
> ---
> arch/x86/virt/vmx/tdx/seamldr.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/virt/vmx/tdx/seamldr.c b/arch/x86/virt/vmx/tdx/seamldr.c
> index 087bdf10a9a7..9cef6fff2a6c 100644
> --- a/arch/x86/virt/vmx/tdx/seamldr.c
> +++ b/arch/x86/virt/vmx/tdx/seamldr.c
> @@ -36,7 +36,7 @@
> #define SEAMLDR_PARAMS_NR_PAGES 16
> #define SEAMLDR_NR_MODULE_PA_ENTRIES (496 + 512 * (SEAMLDR_PARAMS_NR_PAGES - 1))
> #define SEAMLDR_MAX_NR_MODULE_PAGES (SEAMLDR_NR_MODULE_PA_ENTRIES - SEAMLDR_PARAMS_NR_PAGES)
> -#define SEAMLDR_MAX_NR_SIG_PAGES 1
> +#define SEAMLDR_MAX_NR_SIG_PAGES 4
>
> /*
> * The seamldr_params "scenario" field specifies the operation mode:
> @@ -57,7 +57,7 @@ struct seamldr_params {
> u32 version;
> u32 scenario;
> u64 sigstruct_pages_pa_list[SEAMLDR_MAX_NR_SIG_PAGES];
> - u8 reserved[104];
> + u8 reserved[80];
> u64 module_nr_pages;
> u64 module_pages_pa_list[SEAMLDR_NR_MODULE_PA_ENTRIES];
> } __packed;
> @@ -166,6 +166,13 @@ static void populate_seamldr_params(struct seamldr_params *params,
> const u8 *mod, u32 mod_nr_pages)
> {
> params->version = 0;
> + /*
> + * Use version 1 only for multi-page sigstructs, to stay
> + * compatible with old P-SEAMLDRs that lack version 1 support.
> + */
> + if (sig_nr_pages > 1)
> + params->version = 1;
> +
> params->scenario = SEAMLDR_SCENARIO_UPDATE;
> params->module_nr_pages = mod_nr_pages;
>
next prev parent reply other threads:[~2026-11-09 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 13:21 [RFC PATCH v2 0/2] TDX: P-SEAMLDR: Support large TDX modules and sigstructs Chao Gao
2026-11-06 13:21 ` [RFC PATCH v2 1/2] x86/virt/seamldr: Support large TDX module binaries Chao Gao
2026-11-09 22:34 ` Edgecombe, Rick P
2026-11-06 13:21 ` [RFC PATCH v2 2/2] x86/virt/seamldr: Support multiple sigstruct pages Chao Gao
2026-11-09 22:12 ` Edgecombe, Rick P [this message]
2026-11-09 22:19 ` Dave Hansen
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=91506ebc258a9db8b2aa47310a03b60e3c653314.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=arjan.van.de.ven@intel.com \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
--cc=yilun.xu@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
all inboxes | Powered by JetHome®