From: Binbin Wu <binbin.wu@linux.intel.com>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: 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>,
yilun.xu@linux.intel.com, xiaoyao.li@intel.com,
Chao Gao <chao.gao@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/9] x86/virt/tdx: Add SEAMCALL wrappers for IOMMU setup/clear
Date: Wed, 18 Nov 2026 19:02:07 +0800 [thread overview]
Message-ID: <ed90de7e-6019-4d42-bc6e-5b586b460a31@linux.intel.com> (raw)
In-Reply-To: <20261112043054.2664857-2-baolu.lu@linux.intel.com>
On 11/12/2026 12:30 PM, Lu Baolu wrote:
[...]
> +
> +/* No cache flush is needed; hardware keeps caches coherent across KeyIDs. */
Nit:
It's a bit confusing without the all the background.
Once Rick's patch [1] removes tdx_clflush_page() and its comment, a reader may wonder
why this wrapper explains the cache flush but the others don't.
Is it better to drop the comment and explain it in the change log?
[1] https://lore.kernel.org/all/20261015191710.3632302-2-rick.p.edgecombe@intel.com/
> +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(param),
> + };
> + u64 ret;
> +
> + /*
> + * Retry only on TDX_INTERRUPTED_RESUMABLE:
> + *
> + * - TDX_INTERRUPTED_RESUMABLE guarantees forward progress between
> + * calls.
> + * - On TDX_INTERRUPTED_RESUMABLE, all registers except RAX remain
> + * unchanged.
> + *
> + * The ABI spec also allows retrying on TDX_OPERAND_BUSY, but that
> + * status doesn't guarantee forward progress, so retrying could spin
> + * forever. The host serializes all TDH.IOMMU.SETUP and
> + * TDH.IOMMU.CLEAR calls for an IOMMU, so the TDX module should never
> + * report the operand as busy.
> + */
> + 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");
> +
> +u64 tdh_iommu_clear(u64 tdx_iommu_id)
> +{
> + struct tdx_module_args args = {
> + .rcx = tdx_iommu_id,
> + };
> + u64 ret;
> +
> + /*
> + * Don't retry on TDX_OPERAND_BUSY. See the comment in
> + * tdh_iommu_setup().
> + */
> + do {
> + ret = seamcall(TDH_IOMMU_CLEAR, &args);
> + } while (ret == TDX_INTERRUPTED_RESUMABLE);
> +
> + return ret;
> +}
> +EXPORT_SYMBOL_FOR_MODULES(tdh_iommu_clear, "tdx-host");
next prev parent reply other threads:[~2026-11-18 11:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 4:30 [PATCH v3 0/9] coco/tdx-host: Introduce trusted DMA initialization support Lu Baolu
2026-11-12 4:30 ` [PATCH v3 1/9] x86/virt/tdx: Add SEAMCALL wrappers for IOMMU setup/clear Lu Baolu
2026-11-18 11:02 ` Binbin Wu [this message]
2026-11-12 4:30 ` [PATCH v3 2/9] x86/virt/tdx: Read global metadata for trusted IOMMU Lu Baolu
2026-11-12 4:30 ` [PATCH v3 3/9] x86/virt/tdx: Export Dynamic PAMT helpers to tdx-host Lu Baolu
2026-11-12 4:30 ` [PATCH v3 4/9] iommu/vt-d: Add interface for tdx-host when enabling trusted DMA Lu Baolu
2026-11-12 4:30 ` [PATCH v3 5/9] iommu/vt-d: Block GCMD and ECMD while acquired by the TDX module Lu Baolu
2026-11-12 4:30 ` [PATCH v3 6/9] iommu/vt-d: Refuse system suspend " Lu Baolu
2026-11-12 4:30 ` [PATCH v3 7/9] coco/tdx-host: Add skeleton to support PCI link encryption Lu Baolu
2026-11-18 7:16 ` Chao Gao
2026-11-12 4:30 ` [PATCH v3 8/9] coco/tdx-host: Rename tdx-host.c to main.c Lu Baolu
2026-11-12 4:30 ` [PATCH v3 9/9] coco/tdx-host: Enable trusted DMA on IOMMUs on device connect Lu Baolu
2026-11-18 8:11 ` Chao Gao
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=ed90de7e-6019-4d42-bc6e-5b586b460a31@linux.intel.com \
--to=binbin.wu@linux.intel.com \
--cc=baolu.lu@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