From: Jacob Pan <jacob.pan@linux.microsoft.com>
To: Mostafa Saleh <smostafa@google.com>
Cc: iommu@lists.linux.dev, Jason Gunthorpe <jgg@ziepe.ca>,
Nicolin Chen <nicolinc@nvidia.com>,
Kevin Tian <kevin.tian@intel.com>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>, Wei Liu <wei.liu@kernel.org>,
"K . Y . Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Dexuan Cui <decui@microsoft.com>, Long Li <longli@microsoft.com>,
linux-hyperv@vger.kernel.org, Joerg Roedel <joro@8bytes.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Vasant Hegde <vasant.hegde@amd.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
"Aneesh Kumar K . V" <aneesh.kumar@kernel.org>,
Mukesh Rathor <mukeshrathor@microsoft.com>,
John Starks <John.Starks@microsoft.com>,
Souradeep Chakrabarti <schakrabarti@microsoft.com>,
Yu Zhang <zhangyu1@linux.microsoft.com>,
Easwar Hariharan <eahariha@linux.microsoft.com>,
Alex Williamson <alex@shazbot.org>,
jacob.pan@linux.microsoft.com
Subject: Re: [PATCH RFC 1/9] iommu: Introduce external attach domain type
Date: Mon, 26 Oct 2026 16:10:03 -0700 [thread overview]
Message-ID: <20261026161003.00003b71@linux.microsoft.com> (raw)
In-Reply-To: <atiakDqtuED2cTM5@google.com>
Hi Mostafa,
On Wed, 21 Oct 2026 10:57:20 +0000
Mostafa Saleh <smostafa@google.com> wrote:
> On Fri, Sep 25, 2026 at 12:07:34PM -0700, Jacob Pan wrote:
> > Add IOMMU_DOMAIN_EXTERNAL for externally managed domains that move
> > or attach devices to another VM address space provisioned by an
> > external owner, such as a type 1 hypervisor.
> >
> > This is not a paging domain and is not sysfs-selectable as a default
> > domain type. It requires external owner context, such as a vIOMMU.
> >
>
> Can't we use a IOMMU_DOMAIN_BLOCKED domain for that, AFAIU, the host
> never inserts any mapping?
Right, the host does not own or install any mappings.
The external domain type is nevertheless useful for two reasons:
1. It allows the pvIOMMU driver's domain ops to do the MSHV & Xen attach
and detach hypercalls
2. It allows an externally managed device to leverage the normal IOMMUFD
device-to-HWPT attachment interface: VFIO_DEVICE_ATTACH_IOMMUFD_PT
No new ioctls.
It also makes the lifetime and ownership clear for IOMMUFD and
hypervisor, the device can be returned back to host iommufd owned
domains once detached.
In pKVM case, my understanding is that you have a emulated root SMMU
which does not do hypercalls obviously. Then the external attach
is done via an "out of tree uAPI through KVM/VFIO bridge IOCTLs that
proxies those hypercalls."
Therefore, if we were to park the device in blocking domain while doing
external attach (as you suggested), this requires a new PV only uAPI
that must support pkvm, MSHV, and Xen. So it does not fit in the flow
supported by PV IOMMU root driver.
I don't have a better solution for both pv and emulated root IOMMU
drivers. Perhaps others do?
> Thanks,
> Mostafa
>
> > PV IOMMU drivers are expected to use it when moving a device to a
> > guest VM with an already-created S2 IOPT.
> >
> > Assisted-by: GPT-5.6 Sol
> > Signed-off-by: Jacob Pan <jacob.pan@linux.microsoft.com>
> > ---
> > drivers/iommu/iommu.c | 2 ++
> > include/linux/iommu.h | 9 +++++++++
> > 2 files changed, 11 insertions(+)
> >
> > diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
> > index cd1bca7ede9a..d0bd3ef00379 100644
> > --- a/drivers/iommu/iommu.c
> > +++ b/drivers/iommu/iommu.c
> > @@ -220,6 +220,8 @@ static const char
> > *iommu_domain_type_str(unsigned int t) return "Translated";
> > case IOMMU_DOMAIN_PLATFORM:
> > return "Platform";
> > + case IOMMU_DOMAIN_EXTERNAL:
> > + return "External";
> > default:
> > return "Unknown";
> > }
> > diff --git a/include/linux/iommu.h b/include/linux/iommu.h
> > index ac43b8b93f14..ede77b90f0fd 100644
> > --- a/include/linux/iommu.h
> > +++ b/include/linux/iommu.h
> > @@ -188,6 +188,7 @@ enum iommu_domain_cookie_type {
> >
> > #define __IOMMU_DOMAIN_NESTED (1U << 6) /* User-managed
> > address space nested on a stage-2 translation */
> > +#define __IOMMU_DOMAIN_EXTERNAL (1U << 7) /* Externally
> > managed translation */
> > #define IOMMU_DOMAIN_ALLOC_FLAGS ~__IOMMU_DOMAIN_DMA_FQ
> > /*
> > @@ -207,6 +208,13 @@ enum iommu_domain_cookie_type {
> > * represented by mm_struct's.
> > * IOMMU_DOMAIN_PLATFORM - Legacy domain for drivers
> > that do their own
> > * dma_api stuff. Do not use in
> > new drivers.
> > + * IOMMU_DOMAIN_EXTERNAL - Externally managed domain
> > for moving/attaching
> > + * devices to another VM address
> > space
> > + * provisioned by the external
> > owner, such as
> > + * a type 1 hypervisor. This is
> > not a
> > + * sysfs-selectable default
> > domain type; it
> > + * requires external owner
> > context such as a
> > + * vIOMMU.
> > */
> > #define IOMMU_DOMAIN_BLOCKED (0U)
> > #define IOMMU_DOMAIN_IDENTITY (__IOMMU_DOMAIN_PT)
> > @@ -219,6 +227,7 @@ enum iommu_domain_cookie_type {
> > #define IOMMU_DOMAIN_SVA (__IOMMU_DOMAIN_SVA)
> > #define IOMMU_DOMAIN_PLATFORM (__IOMMU_DOMAIN_PLATFORM)
> > #define IOMMU_DOMAIN_NESTED (__IOMMU_DOMAIN_NESTED)
> > +#define IOMMU_DOMAIN_EXTERNAL (__IOMMU_DOMAIN_EXTERNAL)
> >
> > struct iommu_domain {
> > unsigned type;
> > --
> > 2.43.0
> >
> >
next prev parent reply other threads:[~2026-10-26 23:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 19:07 [RFC PATCH 0/9] iommu/iommufd: Add hypervisor external attach Jacob Pan
2026-09-25 19:07 ` [PATCH RFC 1/9] iommu: Introduce external attach domain type Jacob Pan
2026-10-21 10:57 ` Mostafa Saleh
2026-10-26 23:10 ` Jacob Pan [this message]
2026-09-25 19:07 ` [PATCH RFC 2/9] iommufd: Introduce hypervisor vIOMMU type Jacob Pan
2026-09-25 19:07 ` [PATCH RFC 3/9] iommufd: Add external HWPT support Jacob Pan
2026-09-25 19:07 ` [PATCH RFC 4/9] iommufd/selftest: Add hypervisor external attach backend Jacob Pan
2026-09-25 19:07 ` [PATCH RFC 5/9] mshv: Add partition file identity helper Jacob Pan
2026-09-25 19:07 ` [PATCH RFC 6/9] mshv: Add prepare callback for external device attach Jacob Pan
2026-09-25 19:07 ` [PATCH RFC 7/9] iommu/hyperv: Split root IOMMU declarations Jacob Pan
2026-09-25 19:07 ` [PATCH RFC 8/9] iommu/hyperv: Add fd-backed vIOMMU support Jacob Pan
2026-09-25 19:07 ` [PATCH RFC 9/9] iommu/hyperv: Add IOMMUFD external domains Jacob Pan
2026-10-21 10:55 ` [RFC PATCH 0/9] iommu/iommufd: Add hypervisor external attach Mostafa Saleh
2026-10-26 18:49 ` Jacob Pan
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=20261026161003.00003b71@linux.microsoft.com \
--to=jacob.pan@linux.microsoft.com \
--cc=John.Starks@microsoft.com \
--cc=alex@shazbot.org \
--cc=aneesh.kumar@kernel.org \
--cc=arnd@arndb.de \
--cc=decui@microsoft.com \
--cc=eahariha@linux.microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kys@microsoft.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=mukeshrathor@microsoft.com \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=schakrabarti@microsoft.com \
--cc=smostafa@google.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.com \
--cc=wei.liu@kernel.org \
--cc=will@kernel.org \
--cc=zhangyu1@linux.microsoft.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®