mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Xu Yilun <yilun.xu@linux.intel.com>
Cc: baolu.lu@linux.intel.com, iommu@lists.linux.dev, x86@kernel.org,
	linux-coco@lists.linux.dev, kvm@vger.kernel.org,
	Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
	Kiryl Shutsemau <kas@kernel.org>,
	Rick Edgecombe <rick.p.edgecombe@intel.com>,
	xiaoyao.li@intel.com, Chao Gao <chao.gao@intel.com>,
	Binbin Wu <binbin.wu@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] x86/virt/tdx: Add SEAMCALL wrappers for IOMMU setup/clear
Date: Thu, 5 Nov 2026 14:06:27 +0800	[thread overview]
Message-ID: <d52dba58-5f8a-4980-b9d0-0b1e0df48f82@linux.intel.com> (raw)
In-Reply-To: <atBz5cj0wQZv/fLN@yilunxu-OptiPlex-7050>

On 10/15/2026 2:34 PM, Xu Yilun wrote:
> On Thu, Oct 15, 2026 at 09:07:02AM +0800, Lu Baolu wrote:
>> Add SEAMCALL wrappers for TDH.IOMMU.SETUP and TDH.IOMMU.CLEAR.
> 
> We need this patch been reviewed by x86 reviewers. x86 convention
> doesn't start with the implementation, so remove it.
> 
> We can start with a generic description of what the 2 SEAMCALLs are
> doing in general and why. Maybe move some of your description in next
> paragraph ahead.

Agreed.

> 
>>
>> TDH.IOMMU.SETUP transitions an IOMMU and related I/O stack into Secure
>> TDX Mode. During this transition, the TDX module validates and protects
>> relevant I/O resources from further untrusted host access, providing the
>> trusted foundation required before enabling TEE-IO security protocols
>> (e.g. SPDM/IDE).
>>
>> TDH.IOMMU.CLEAR performs the reverse operation and tears down the Secure
>> TDX Mode state for the target IOMMU.
>>
>> The caller is responsible for allocating the required pages and
>> populating the parameter page in the ABI-defined format.
>>
>> See Intel TDX Connect ABI Specification [1], Section 3.2 (TDX Connect
>> Host-Side (SEAMCALL) Interface Functions).
>>
>> Thanks to Xu Yilun for the initial draft.
> 
> Feel free to drop it. Not that important.

Dropped.

> 
>>
>> [1] https://cdrdv2.intel.com/v1/dl/getContent/858625
>>
>> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
>> ---
>>   arch/x86/include/asm/tdx.h  |  2 ++
>>   arch/x86/virt/vmx/tdx/tdx.h |  2 ++
>>   arch/x86/virt/vmx/tdx/tdx.c | 56 +++++++++++++++++++++++++++++++++++++
>>   3 files changed, 60 insertions(+)
>>
>> diff --git a/arch/x86/include/asm/tdx.h b/arch/x86/include/asm/tdx.h
>> index 89e97d5761d8..8b5411d3eb67 100644
>> --- a/arch/x86/include/asm/tdx.h
>> +++ b/arch/x86/include/asm/tdx.h
>> @@ -176,6 +176,8 @@ u64 tdh_mem_page_remove(struct tdx_td *td, u64 gpa, enum pg_level level, u64 *ex
>>   u64 tdh_phymem_cache_wb(bool resume);
>>   u64 tdh_phymem_page_wbinvd_tdr(struct tdx_td *td);
>>   u64 tdh_phymem_page_wbinvd_hkid(u64 hkid, kvm_pfn_t pfn);
>> +u64 tdh_iommu_setup(u64 reg_base, void *root, u64 *tdx_iommu_id);
>> +u64 tdh_iommu_clear(u64 tdx_iommu_id);
>>   #else
>>   static inline void tdx_init(void) { }
>>   static inline u32 tdx_get_nr_guest_keyids(void) { return 0; }
>> diff --git a/arch/x86/virt/vmx/tdx/tdx.h b/arch/x86/virt/vmx/tdx/tdx.h
>> index bdfd0e1e337a..d7beb42cf972 100644
>> --- a/arch/x86/virt/vmx/tdx/tdx.h
>> +++ b/arch/x86/virt/vmx/tdx/tdx.h
>> @@ -49,6 +49,8 @@
>>   #define TDH_SYS_SHUTDOWN		52
>>   #define TDH_SYS_UPDATE			53
>>   #define TDH_SYS_DISABLE			69
>> +#define TDH_IOMMU_SETUP			128
>> +#define TDH_IOMMU_CLEAR			129
>>   
>>   /*
>>    * SEAMCALL leaf:
>> diff --git a/arch/x86/virt/vmx/tdx/tdx.c b/arch/x86/virt/vmx/tdx/tdx.c
>> index 1b9ff749dd8e..5d31c1b0890a 100644
>> --- a/arch/x86/virt/vmx/tdx/tdx.c
>> +++ b/arch/x86/virt/vmx/tdx/tdx.c
>> @@ -2034,3 +2034,59 @@ void tdx_sys_disable(void)
>>   	if (ret && (ret & TDX_SW_ERROR) != TDX_SW_ERROR)
>>   		pr_err("TDH.SYS.DISABLE failed: 0x%016llx\n", ret);
>>   }
>> +
>> +/*
>> + * Wrapper for TDH.IOMMU.SETUP leaf, which transitions the IOMMU and related
>> + * I/O stack into Secure TDX Mode.
> 
> Other tdh_*() wrappers don't have the general descriptions. We all know
> these are wrappers for some SEAMCALL leafs.
> 
> So if there is no special thing to note, remove it.

Removed for both wrappers.

> 
>> + *
>> + * The @root page format is defined by the TDX Connect ABI spec (Table 3.35,
>> + * Structure of IOMMU_MT Parameter): the first two entries describe the size
>> + * and HPA (Host Physical Address) of the two contiguous buffers for the
>> + * invalidation queue; the remaining entries provide HPAs of
>> + * IOMMU_MT_PAGES_COUNT metadata pages. IOMMU_MT_PAGES_COUNT is obtained from
>> + * trusted IOMMU global metadata.
>> + */
>> +u64 tdh_iommu_setup(u64 reg_base, void *root, u64 *tdx_iommu_id)
> 
> IIUC, the void *root is a vague type, no type safty. Is it better we
> define an explicit structure that mirrors the in-memory ABI? Something
> like:
> 
>    struct tdx_iommu_metadata {
> 	u64 iq1_pa;
> 	u64 iq2_pa;
> 	DECLARE_FLEX_ARRAY(u64, mt_pa);
>    };
> 
> Or,
> 
>    struct tdx_iommu_metadata {
> 	u64 iq1_pa;
> 	u64 iq2_pa;
> 	u64 mt_pa[510];
>    };
> 
>    static_assert(sizeof(struct tdx_iommu_metadata) == 4096);

Good point. I updated the code with the following:

   #define TDX_IOMMU_MT_IQ_NR	2
   #define TDX_IOMMU_MT_MAX_PAGES	(PAGE_SIZE / sizeof(u64) - 
TDX_IOMMU_MT_IQ_NR)

   /* IOMMU_MT parameter page for TDH.IOMMU.SETUP (ABI spec Table 3.35). */
   struct tdx_iommu_mt_param {
       u64 iq[TDX_IOMMU_MT_IQ_NR];	/* HPA | number of 4K pages */
       u64 mt[TDX_IOMMU_MT_MAX_PAGES];	/* HPA of each metadata page */
   };
   static_assert(sizeof(struct tdx_iommu_mt_param) == PAGE_SIZE);

   u64 tdh_iommu_setup(u64 reg_base, struct tdx_iommu_mt_param *param,
               u64 *tdx_iommu_id);

> 
>> +{
>> +	struct tdx_module_args args = {
>> +		.rcx = reg_base,
>> +		.rdx = __pa(root),
>> +	};
>> +	u64 ret;
>> +
>> +	/*
>> +	 * Don't loop forever:
>> +	 *
>> +	 *  - TDX_INTERRUPTED_RESUMABLE guarantees forward progress between
>> +	 *    calls.
>> +	 *  - On TDX_INTERRUPTED_RESUMABLE, all registers except RAX remain
>> +	 *    unchanged.
>> +	 */
>> +	do {
>> +		ret = seamcall_ret(TDH_IOMMU_SETUP, &args);
>> +	} while (ret == TDX_INTERRUPTED_RESUMABLE);
>> +
>> +	*tdx_iommu_id = args.rcx;
>> +
>> +	return ret;
>> +}
>> +EXPORT_SYMBOL_FOR_MODULES(tdh_iommu_setup, "tdx-host");
>> +
>> +/*
>> + * Wrapper for TDH.IOMMU.CLEAR leaf, which terminates Secure TDX Mode for the
>> + * target IOMMU and restores control of related hardware resources to the host.
>> + */
>> +u64 tdh_iommu_clear(u64 tdx_iommu_id)
>> +{
>> +	struct tdx_module_args args = {
>> +		.rcx = tdx_iommu_id,
>> +	};
>> +	u64 ret;
>> +
>> +	do {
>> +		ret = seamcall(TDH_IOMMU_CLEAR, &args);
>> +	} while (ret == TDX_INTERRUPTED_RESUMABLE);
>> +
>> +	return ret;
>> +}
>> +EXPORT_SYMBOL_FOR_MODULES(tdh_iommu_clear, "tdx-host");
>> -- 
>> 2.43.0
>>

Thanks,
baolu

  reply	other threads:[~2026-11-05  6:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15  1:07 [PATCH v2 0/4] coco/tdx-host: Introduce trusted DMA initialization support Lu Baolu
2026-10-15  1:07 ` [PATCH v2 1/4] x86/virt/tdx: Add SEAMCALL wrappers for IOMMU setup/clear Lu Baolu
2026-10-15  6:34   ` Xu Yilun
2026-11-05  6:06     ` Baolu Lu [this message]
2026-10-15  1:07 ` [PATCH v2 2/4] x86/virt/tdx: Read global metadata for trusted IOMMU Lu Baolu
2026-10-15  6:47   ` Xu Yilun
2026-10-16  7:59     ` Tian, Kevin
2026-10-15  1:07 ` [PATCH v2 3/4] iommu/vt-d: Add an API for tdx-host when enabling trusted DMA Lu Baolu
2026-10-15  1:07 ` [PATCH v2 4/4] coco/tdx-host: Initialize trusted DMA on all capable IOMMUs Lu Baolu
2026-10-15  8:31   ` Xu Yilun
2026-10-15 17:37     ` Jason Gunthorpe
2026-10-16  7:03       ` Baolu Lu
2026-10-16  7:17         ` Tian, Kevin
2026-10-16 14:58           ` Jason Gunthorpe
2026-10-19  8:16             ` Baolu Lu
2026-10-22  4:02             ` Tian, Kevin
2026-10-19  8:12           ` Baolu Lu
2026-10-22  4:07             ` Tian, Kevin
2026-11-05  6:10               ` Baolu Lu
2026-10-16 14:58         ` Jason Gunthorpe
2026-10-19  8:17           ` Baolu Lu
2026-10-19  7:03   ` Chao Gao
2026-10-19  8:40     ` Baolu Lu

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=d52dba58-5f8a-4980-b9d0-0b1e0df48f82@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=binbin.wu@linux.intel.com \
    --cc=chao.gao@intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=kas@kernel.org \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rick.p.edgecombe@intel.com \
    --cc=x86@kernel.org \
    --cc=xiaoyao.li@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®