From: Baolu Lu <baolu.lu@linux.intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"x86@kernel.org" <x86@kernel.org>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Cc: baolu.lu@linux.intel.com, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Dave Hansen <dave.hansen@linux.intel.com>,
Kiryl Shutsemau <kas@kernel.org>,
"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"yilun.xu@linux.intel.com" <yilun.xu@linux.intel.com>,
"Li, Xiaoyao" <xiaoyao.li@intel.com>,
"Gao, Chao" <chao.gao@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] iommu/vt-d: Introduce trusted DMA initialization support
Date: Sat, 19 Sep 2026 12:04:27 +0800 [thread overview]
Message-ID: <48f71e6e-7240-428d-a8a7-31542a880a18@linux.intel.com> (raw)
In-Reply-To: <CO1PR11MB48351B13F0143DE043EF15378C872@CO1PR11MB4835.namprd11.prod.outlook.com>
On 9/18/2026 10:30 AM, Tian, Kevin wrote:
>> From: Lu Baolu <baolu.lu@linux.intel.com>
>> Sent: Tuesday, September 15, 2026 3:42 PM
>>
>> Hi,
>>
>> This series adds Intel VT-d trusted extension support to the host Intel
>> IOMMU driver as groundwork for TEE I/O trusted DMA (e.g. TDX Connect).
>>
>> The trusted extension introduces a parallel, extension-specific path for
>> trusted DMA assets used by confidential device assignment. Existing VT-d
>> functionality remains unchanged for regular host DMA paths.
>>
>> From the TDX Connect architecture perspective, VT-d is enhanced with:
>>
>> 1) Trusted DMA translation root table
>> - A second root-table address register, restricted to SEAM SAI.
>> - Programmed by the TDX module with the root of TDX-managed DMA
>> translation tables for TD-assigned devices.
>>
>> 2) Trusted invalidation queue
>> - A second invalidation-queue address register plus dedicated
>> head/tail registers, also restricted to SEAM SAI.
>>
>> 3) IOTLB / DID isolation
>> - When TDX Connect is enabled, VT-d restricts VMM DID usage and
>> reserves the DID MSB namespace bit for TDX-module use.
>>
>> This posting focuses on VT-d-side enablement only: it enables those
>> extension-defined resources and control points while preserving existing
>> host VT-d behavior for non-trusted flows. Higher-layer integration
>> (TDX guest/device flows) will be posted separately.
>>
>
> Jason had a comment on this from another thread [1]:
>
> "
> Okay, so I saw the driver posting for basic iommu support, can we try
> to rework that to be split out like Aneesh is doing so everything
> about TDX calls lives in tsm and intel iommu only provides a small API
> surface to exchange whatever details are needed to bootstrap TDX
> module?
> "
>
> [1] https://lore.kernel.org/all/20260916123954.GC3196566@ziepe.ca/
Yes, I will head in this direction in the next version.
Thanks,
baolu
prev parent reply other threads:[~2026-09-19 4:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 7:42 Lu Baolu
2026-09-15 7:42 ` [PATCH 1/5] x86/virt/tdx: Add SEAMCALL wrappers for IOMMU setup/clear Lu Baolu
2026-09-15 7:42 ` [PATCH 2/5] x86/virt/tdx: Read global metadata for trusted IOMMU Lu Baolu
2026-09-15 7:42 ` [PATCH 3/5] iommu/vt-d: Add interfaces for trusted DMA initialization Lu Baolu
2026-09-15 7:42 ` [PATCH 4/5] iommu/vt-d: Add helpers to set up and tear down TDX extensions Lu Baolu
2026-09-15 7:42 ` [PATCH 5/5] iommu/vt-d: Reserve MSB of domain ID space for TDX module Lu Baolu
2026-09-18 2:30 ` [PATCH 0/5] iommu/vt-d: Introduce trusted DMA initialization support Tian, Kevin
2026-09-19 4:04 ` Baolu Lu [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=48f71e6e-7240-428d-a8a7-31542a880a18@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=chao.gao@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--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=robin.murphy@arm.com \
--cc=will@kernel.org \
--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®