From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "Hansen, Dave" <dave.hansen@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"yilun.xu@linux.intel.com" <yilun.xu@linux.intel.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>
Cc: "Xu, Yilun" <yilun.xu@intel.com>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"kas@kernel.org" <kas@kernel.org>,
"nik.borisov@suse.com" <nik.borisov@suse.com>,
"tony.lindgren@linux.intel.com" <tony.lindgren@linux.intel.com>,
"binbin.wu@linux.intel.com" <binbin.wu@linux.intel.com>
Subject: Re: [PATCH v6] x86/virt/tdx: Formalize SEAMCALL leaf version encoding support
Date: Thu, 10 Sep 2026 20:16:05 +0000 [thread overview]
Message-ID: <49a5893fd1d3748b4b8c5e1842f52ad29b060760.camel@intel.com> (raw)
In-Reply-To: <20260910104347.625378-1-yilun.xu@linux.intel.com>
On Thu, 2026-09-10 at 18:43 +0800, Xu Yilun wrote:
> The TDX architecture includes a syscall-like ABI for OSes to communicate
> with SEAM mode software. This ABI has the concept of a "leaf". Each leaf
> is roughly analogous to a Linux syscall: it has a set of register
> arguments and does one logical thing like adding a page of memory to a
> VM or running a VM. The TDX architecture refers to this interface
> function as a "SEAMCALL leaf".
>
> Just like syscalls, the TDX architecture wants to evolve the ABI to
> extend functionality while keeping compatibility. But unlike syscalls,
> which do this by picking a totally new syscall number, the ABI encodes
> the "version" number directly into the bits of a register argument. So
> instead of openatN being whatever the next free number is, the SEAMCALL
> leaf number and version number are encoded into certain bits in how the
> RAX register is defined in the ABI.
>
> In Linux, several seamcall*() wrappers have been introduced to invoke
> SEAMCALL leafs. They all take a u64 "fn" argument for the leaf number
> which eventually get set in the register. As above, the version number
> lives in the same register as the leaf number. So callers that want to
> select a specific version of the leaf, can jam it in the right place in
> the register by passing it in the "fn" argument. Today only the caller
> of TDH.VP.INIT does this hack, but future kernel changes will need to
> select versions for more SEAMCALL leafs, so a less hacky solution is
> needed.
Only nit is that this would probably read a little bit smoother as two
sentences. Everything else looks good.
Reviewed-by: Rick Edgecombe <rick.p.edgecombe@intel.com>
prev parent reply other threads:[~2026-09-10 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 10:43 Xu Yilun
2026-09-10 20:16 ` Edgecombe, Rick P [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=49a5893fd1d3748b4b8c5e1842f52ad29b060760.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=binbin.wu@linux.intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kas@kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=nik.borisov@suse.com \
--cc=tony.lindgren@linux.intel.com \
--cc=x86@kernel.org \
--cc=yilun.xu@intel.com \
--cc=yilun.xu@linux.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®