mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Nikolay Borisov <nik.borisov@suse.com>,
	Xu Yilun <yilun.xu@linux.intel.com>,
	Kiryl Shutsemau <kas@kernel.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
	rick.p.edgecombe@intel.com, dave.hansen@linux.intel.com,
	yilun.xu@intel.com, chao.gao@intel.com, djbw@kernel.org,
	linux-coco@lists.linux.dev, peter.fang@intel.com,
	xiaoyao.li@intel.com
Subject: Re: [PATCH v2] x86/virt/tdx: Formalize SEAMCALL version encoding support
Date: Fri, 17 Jul 2026 06:10:47 -0700	[thread overview]
Message-ID: <205dee48-3238-4d86-adc3-365a8a5d62b8@intel.com> (raw)
In-Reply-To: <90685b93-e13e-4509-98f3-4509381d4981@suse.com>

On 7/17/26 01:21, Nikolay Borisov wrote:
> At the end of the day the layout of args is the software API that is
> presented to the rest of the system, the ABI is a low level detail
> handled in TDX_MODULE_CALL.

Yep, that's my basic view of it too.

I don't feel strongly about where the structure is translated over to
the hardware registers of the actual module ABI call, as long as it's
consistent and centralized.

  reply	other threads:[~2026-07-17 13:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 17:03 Xu Yilun
2026-07-08 18:03 ` Dave Hansen
2026-07-09 10:16   ` Xu Yilun
2026-07-10 16:21   ` Kiryl Shutsemau
2026-07-10 16:48     ` Dave Hansen
2026-07-13  9:40       ` Kiryl Shutsemau
2026-07-17  4:31         ` Xu Yilun
2026-07-17  8:21           ` Nikolay Borisov
2026-07-17 13:10             ` Dave Hansen [this message]
2026-07-10 15:56 ` Kiryl Shutsemau
2026-07-13  9:21   ` Xu Yilun
2026-07-13 11:38     ` Kiryl Shutsemau
2026-07-14 11:18       ` Xu Yilun

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=205dee48-3238-4d86-adc3-365a8a5d62b8@intel.com \
    --to=dave.hansen@intel.com \
    --cc=chao.gao@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=djbw@kernel.org \
    --cc=kas@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=x86@kernel.org \
    --cc=xiaoyao.li@intel.com \
    --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