Skip to contentSkip to conversation

iommufd support allocating nested parent domain

PATCH Superseded Yi Liu 5 participants 27 messages Sep 19, 2023 – Sep 26, 2023

Subsystems (5)

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore

Yi Liu

author
#0 lore raw

cover iommufd support allocating nested parent domain

IOMMU hardwares that support nested translation would have two stages address translation (normally mentioned as stage-1 and stage-2). The page table formats of the stage-1 and stage-2 can be different. e.g., VT-d has different page table formats for stage-1 and stage-2.

Nested parent domain is the iommu domain used to represent the stage-2 translation. In IOMMUFD, both stage-1 and stage-2 translation are tracked as HWPT (a.k.a. iommu domain). Stage-2 HWPT is parent of stage-1 HWPT as stage-1 cannot work alone in nested translation. In the cases of stage-1 and stage-2 page table format are different, the parent HWPT should use exactly the stage-2 page table format. However, the existing kernel hides the format selection in iommu drivers, so the domain allocated via IOMMU_HWPT_ALLOC can use either stage-1 page table format or stage-2 page table format, there is no guarantees for it.

To enforce the page table format of the nested parent domain, this series introduces a new iommu op (domain_alloc_user) which can accept user flags to allocate domain as userspace requires. It also converts IOMMUFD to use the new domain_alloc_user op for domain allocation if supported, then extends the IOMMU_HWPT_ALLOC ioctl to pass down a NEST_PARENT flag to allocate a HWPT which can be used as parent. This series implements the new op in Intel iommu driver to have a complete picture. It is a preparation for adding nesting support in IOMMUFD/IOMMU.

Complete code can be found:
https://github.com/yiliu1765/iommufd/tree/iommufd_alloc_user_v1

Regards,
Yi Liu

Yi Liu (6):
iommu: Add new iommu op to create domains owned by userspace iommufd/hw_pagetable: Use domain_alloc_user op for domain allocation iommufd/hw_pagetable: Accepts user flags for domain allocation iommufd/hw_pagetable: Support allocating nested parent domain iommufd/selftest: Add domain_alloc_user() support in iommu mock iommu/vt-d: Add domain_alloc_user op

 drivers/iommu/intel/iommu.c                   | 20 ++++++++++++
 drivers/iommu/iommufd/device.c                |  2 +-
 drivers/iommu/iommufd/hw_pagetable.c          | 31 ++++++++++++++-----
 drivers/iommu/iommufd/iommufd_private.h       |  3 +-
 drivers/iommu/iommufd/selftest.c              | 16 ++++++++++
 include/linux/iommu.h                         |  8 +++++
 include/uapi/linux/iommufd.h                  | 12 ++++++-
 tools/testing/selftests/iommu/iommufd.c       | 24 +++++++++++---
 .../selftests/iommu/iommufd_fail_nth.c        |  2 +-
 tools/testing/selftests/iommu/iommufd_utils.h | 11 +++++--
 10 files changed, 111 insertions(+), 18 deletions(-)
Signature · 1 line
2.34.1
author
#1 lore raw

PATCH 1/6 iommu: Add new iommu op to create domains owned by userspace

Introduce a new iommu_domain op to create domains owned by userspace, e.g. through IOMMUFD. These domains have a few different properties compares to kernel owned domains:

- They may be UNMANAGED domains, but created with special parameters. For instance aperture size changes/number of levels, different IOPTE formats, or other things necessary to make a vIOMMU work

- We have to track all the memory allocations with GFP_KERNEL_ACCOUNT to make the cgroup sandbox stronger

- Device-specialty domains, such as NESTED domains can be created by IOMMUFD.

The new op clearly says the domain is being created by IOMMUFD, that the domain is intended for userspace use, and it provides a way to pass user flags or a driver specific uAPI structure to customize the created domain to exactly what the vIOMMU userspace driver requires.

iommu drivers that cannot support VFIO/IOMMUFD should not support this op. This includes any driver that cannot provide a fully functional UNMANAGED domain.

This new op for now is only supposed to be used by IOMMUFD, hence no wrapper for it. IOMMUFD would call the callback directly. As for domain free, IOMMUFD would use iommu_domain_free().

---
 include/linux/iommu.h        |  8 ++++++++
 include/uapi/linux/iommufd.h | 12 +++++++++++-
 2 files changed, 19 insertions(+), 1 deletion(-)
include/linux/iommu.h +8 -0
index c50a769d569a..660dc1931dc9 100644
@@ -235,6 +235,13 @@ struct iommu_iotlb_gather {
  *           use. The information type is one of enum iommu_hw_info_type defined
  *           in include/uapi/linux/iommufd.h.
  * @domain_alloc: allocate iommu domain
+ * @domain_alloc_user: Allocate an iommu domain corresponding to the input
+ *                     parameters like flags defined as enum iommufd_ioas_map_flags
+ *                     in include/uapi/linux/iommufd.h. Different from the
+ *                     domain_alloc op, it requires iommu driver to fully
+ *                     initialize a new domain including the generic iommu_domain
+ *                     struct. Upon success, a domain is returned. Upon failure,
+ *                     ERR_PTR must be returned.
  * @probe_device: Add device to iommu driver handling
  * @release_device: Remove device from iommu driver handling
  * @probe_finalize: Do final setup work after the device is added to an IOMMU
@@ -267,6 +274,7 @@ struct iommu_ops {
 
 	/* Domain allocation and freeing by the iommu driver */
 	struct iommu_domain *(*domain_alloc)(unsigned iommu_domain_type);
+	struct iommu_domain *(*domain_alloc_user)(struct device *dev, u32 flags);
 
 	struct iommu_device *(*probe_device)(struct device *dev);
 	void (*release_device)(struct device *dev);
include/uapi/linux/iommufd.h +11 -1
index b4ba0c0cbab6..4a7c5c8fdbb4 100644
@@ -347,10 +347,20 @@ struct iommu_vfio_ioas {
 };
 #define IOMMU_VFIO_IOAS _IO(IOMMUFD_TYPE, IOMMUFD_CMD_VFIO_IOAS)
 
+/**
+ * enum iommufd_hwpt_alloc_flags - Flags for HWPT allocation
+ * @IOMMU_HWPT_ALLOC_NEST_PARENT: If set, allocate a domain which can serve
+ *                                as the parent domain in the nesting
+ *                                configuration.
+ */
+enum iommufd_hwpt_alloc_flags {
+	IOMMU_HWPT_ALLOC_NEST_PARENT = 1 << 0,
+};
+
 /**
  * struct iommu_hwpt_alloc - ioctl(IOMMU_HWPT_ALLOC)
  * @size: sizeof(struct iommu_hwpt_alloc)
- * @flags: Must be 0
+ * @flags: Combination of enum iommufd_hwpt_alloc_flags
  * @dev_id: The device to allocate this HWPT for
  * @pt_id: The IOAS to connect this HWPT to
  * @out_hwpt_id: The ID of the new HWPT
Signature · 1 line
2.34.1
maintainer
#2 lore raw

RE: [PATCH 1/6] iommu: Add new iommu op to create domains owned by userspace

Quoted 8 lines

From: Liu, Yi L <[email protected]>
Sent: Tuesday, September 19, 2023 5:25 PM

(quoted diff) +0 -0
@@ -235,6 +235,13 @@ struct iommu_iotlb_gather {
  *           use. The information type is one of enum iommu_hw_info_type

defined
* in include/uapi/linux/iommufd.h.
* @domain_alloc: allocate iommu domain

Given now we have two @alloc ops it'd be clearer to also update the comment here so the explanation for @domain_alloc_user() is easier to be understood, e.g.:

@domain_alloc: allocate and return an iommu domain if success. Otherwise
NULL is returned. The domain is not fully initialized until the caller iommu_domain_alloc() returns.

Quoted 5 lines

+ * @domain_alloc_user: Allocate an iommu domain corresponding to the input
+ * parameters like flags defined as enum
iommufd_ioas_map_flags
+ * in include/uapi/linux/iommufd.h. Different from the

"to the input parameters as defined in include/uapi/linux/iommufd.h".

Quoted 2 lines

+ * domain_alloc op, it requires iommu driver to fully
+ * initialize a new domain including the generic iommu_domain

"Unlike @domain_alloc, it is called only by iommufd and must fully initialize the new domain before return".

*domain* here already refers to the generic iommu_domain struct.

author
#3 lore raw

Re: [PATCH 1/6] iommu: Add new iommu op to create domains owned by userspace

Quoted 25 lines · Kevin
Quoted 8 lines

From: Liu, Yi L <[email protected]>
Sent: Tuesday, September 19, 2023 5:25 PM

(quoted diff) +0 -0
@@ -235,6 +235,13 @@ struct iommu_iotlb_gather {
   *           use. The information type is one of enum iommu_hw_info_type

defined
* in include/uapi/linux/iommufd.h.
* @domain_alloc: allocate iommu domain

Given now we have two @alloc ops it'd be clearer to also update the comment here so the explanation for @domain_alloc_user() is easier to be understood, e.g.:

@domain_alloc: allocate and return an iommu domain if success. Otherwise
NULL is returned. The domain is not fully initialized until the caller iommu_domain_alloc() returns.

Quoted 5 lines

+ * @domain_alloc_user: Allocate an iommu domain corresponding to the input
+ * parameters like flags defined as enum
iommufd_ioas_map_flags
+ * in include/uapi/linux/iommufd.h. Different from the

"to the input parameters as defined in include/uapi/linux/iommufd.h".

Quoted 8 lines
Quoted 2 lines

+ * domain_alloc op, it requires iommu driver to fully
+ * initialize a new domain including the generic iommu_domain

"Unlike @domain_alloc, it is called only by iommufd and must fully initialize the new domain before return".

*domain* here already refers to the generic iommu_domain struct.

above comment well received.

Signature · 2 lines
Regards,
Yi Liu
author
#4 lore raw

PATCH 2/6 iommufd/hw_pagetable: Use domain_alloc_user op for domain allocation

In reply to Yi Liu

This makes IOMMUFD to use iommu_domain_alloc_user() for iommu_domain creation as IOMMUFD needs to support iommu_domain allocation with parameters from userspace in nested support. If the iommu driver doesn't provide domain_alloc_user callback then IOMMUFD falls back to use iommu_domain_alloc().

---
 drivers/iommu/iommufd/hw_pagetable.c | 19 +++++++++++++++----
 1 file changed, 15 insertions(+), 4 deletions(-)
drivers/iommu/iommufd/hw_pagetable.c +15 -4
index cf2c1504e20d..48874f896521 100644
@@ -5,6 +5,7 @@
 #include <linux/iommu.h>
 #include <uapi/linux/iommufd.h>
 
+#include "../iommu-priv.h"
 #include "iommufd_private.h"
 
 void iommufd_hw_pagetable_destroy(struct iommufd_object *obj)
@@ -74,6 +75,7 @@ struct iommufd_hw_pagetable *
 iommufd_hw_pagetable_alloc(struct iommufd_ctx *ictx, struct iommufd_ioas *ioas,
 			   struct iommufd_device *idev, bool immediate_attach)
 {
+	const struct iommu_ops *ops = dev_iommu_ops(idev->dev);
 	struct iommufd_hw_pagetable *hwpt;
 	int rc;
 
@@ -88,10 +90,19 @@ iommufd_hw_pagetable_alloc(struct iommufd_ctx *ictx, struct iommufd_ioas *ioas,
 	refcount_inc(&ioas->obj.users);
 	hwpt->ioas = ioas;
 
-	hwpt->domain = iommu_domain_alloc(idev->dev->bus);
-	if (!hwpt->domain) {
-		rc = -ENOMEM;
-		goto out_abort;
+	if (ops->domain_alloc_user) {
+		hwpt->domain = ops->domain_alloc_user(idev->dev, 0);
+		if (IS_ERR(hwpt->domain)) {
+			rc = PTR_ERR(hwpt->domain);
+			hwpt->domain = NULL;
+			goto out_abort;
+		}
+	} else {
+		hwpt->domain = iommu_domain_alloc(idev->dev->bus);
+		if (!hwpt->domain) {
+			rc = -ENOMEM;
+			goto out_abort;
+		}
 	}
 
 	/*
Signature · 1 line
2.34.1
author
#5 lore raw

PATCH 3/6 iommufd/hw_pagetable: Accepts user flags for domain allocation

In reply to Yi Liu

This extends iommufd_hw_pagetable_alloc() to accepts user flags.

---
 drivers/iommu/iommufd/device.c          | 2 +-
 drivers/iommu/iommufd/hw_pagetable.c    | 9 ++++++---
 drivers/iommu/iommufd/iommufd_private.h | 3 ++-
 3 files changed, 9 insertions(+), 5 deletions(-)
drivers/iommu/iommufd/device.c +1 -1
index ce78c3671539..e88fa73a45e6 100644
@@ -540,7 +540,7 @@ iommufd_device_auto_get_domain(struct iommufd_device *idev,
 	}
 
 	hwpt = iommufd_hw_pagetable_alloc(idev->ictx, ioas, idev,
-					  immediate_attach);
+					  0, immediate_attach);
 	if (IS_ERR(hwpt)) {
 		destroy_hwpt = ERR_CAST(hwpt);
 		goto out_unlock;
drivers/iommu/iommufd/hw_pagetable.c +6 -3
index 48874f896521..5be7a31cbd9c 100644
@@ -61,6 +61,7 @@ int iommufd_hw_pagetable_enforce_cc(struct iommufd_hw_pagetable *hwpt)
  * @ictx: iommufd context
  * @ioas: IOAS to associate the domain with
  * @idev: Device to get an iommu_domain for
+ * @flags: Flags from userspace
  * @immediate_attach: True if idev should be attached to the hwpt
  *
  * Allocate a new iommu_domain and return it as a hw_pagetable. The HWPT
@@ -73,7 +74,8 @@ int iommufd_hw_pagetable_enforce_cc(struct iommufd_hw_pagetable *hwpt)
  */
 struct iommufd_hw_pagetable *
 iommufd_hw_pagetable_alloc(struct iommufd_ctx *ictx, struct iommufd_ioas *ioas,
-			   struct iommufd_device *idev, bool immediate_attach)
+			   struct iommufd_device *idev, u32 flags,
+			   bool immediate_attach)
 {
 	const struct iommu_ops *ops = dev_iommu_ops(idev->dev);
 	struct iommufd_hw_pagetable *hwpt;
@@ -91,7 +93,7 @@ iommufd_hw_pagetable_alloc(struct iommufd_ctx *ictx, struct iommufd_ioas *ioas,
 	hwpt->ioas = ioas;
 
 	if (ops->domain_alloc_user) {
-		hwpt->domain = ops->domain_alloc_user(idev->dev, 0);
+		hwpt->domain = ops->domain_alloc_user(idev->dev, flags);
 		if (IS_ERR(hwpt->domain)) {
 			rc = PTR_ERR(hwpt->domain);
 			hwpt->domain = NULL;
@@ -166,7 +168,8 @@ int iommufd_hwpt_alloc(struct iommufd_ucmd *ucmd)
 	}
 
 	mutex_lock(&ioas->mutex);
-	hwpt = iommufd_hw_pagetable_alloc(ucmd->ictx, ioas, idev, false);
+	hwpt = iommufd_hw_pagetable_alloc(ucmd->ictx, ioas,
+					  idev, cmd->flags, false);
 	if (IS_ERR(hwpt)) {
 		rc = PTR_ERR(hwpt);
 		goto out_unlock;
drivers/iommu/iommufd/iommufd_private.h +2 -1
index 2c58670011fe..3064997a0181 100644
@@ -242,7 +242,8 @@ struct iommufd_hw_pagetable {
 
 struct iommufd_hw_pagetable *
 iommufd_hw_pagetable_alloc(struct iommufd_ctx *ictx, struct iommufd_ioas *ioas,
-			   struct iommufd_device *idev, bool immediate_attach);
+			   struct iommufd_device *idev, u32 flags,
+			   bool immediate_attach);
 int iommufd_hw_pagetable_enforce_cc(struct iommufd_hw_pagetable *hwpt);
 int iommufd_hw_pagetable_attach(struct iommufd_hw_pagetable *hwpt,
 				struct iommufd_device *idev);
Signature · 1 line
2.34.1
author
#7 lore raw

PATCH 4/6 iommufd/hw_pagetable: Support allocating nested parent domain

In reply to Yi Liu

This extends IOMMU_HWPT_ALLOC to allocate domains used as parent (stage-2) in nested translation.

---
 drivers/iommu/iommufd/hw_pagetable.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/iommu/iommufd/hw_pagetable.c +4 -1
index 5be7a31cbd9c..26a8a818ffa3 100644
@@ -83,6 +83,9 @@ iommufd_hw_pagetable_alloc(struct iommufd_ctx *ictx, struct iommufd_ioas *ioas,
 
 	lockdep_assert_held(&ioas->mutex);
 
+	if ((flags & IOMMU_HWPT_ALLOC_NEST_PARENT) && !ops->domain_alloc_user)
+		return ERR_PTR(-EOPNOTSUPP);
+
 	hwpt = iommufd_object_alloc(ictx, hwpt, IOMMUFD_OBJ_HW_PAGETABLE);
 	if (IS_ERR(hwpt))
 		return hwpt;
@@ -154,7 +157,7 @@ int iommufd_hwpt_alloc(struct iommufd_ucmd *ucmd)
 	struct iommufd_ioas *ioas;
 	int rc;
 
-	if (cmd->flags || cmd->__reserved)
+	if (cmd->flags & ~IOMMU_HWPT_ALLOC_NEST_PARENT || cmd->__reserved)
 		return -EOPNOTSUPP;
 
 	idev = iommufd_get_device(ucmd, cmd->dev_id);
Signature · 1 line
2.34.1
maintainer
#8 lore raw

Re: [PATCH 4/6] iommufd/hw_pagetable: Support allocating nested parent domain

Quoted 23 lines · Yi Liu

This extends IOMMU_HWPT_ALLOC to allocate domains used as parent (stage-2) in nested translation.

---
  drivers/iommu/iommufd/hw_pagetable.c | 5 ++++-
  1 file changed, 4 insertions(+), 1 deletion(-)
drivers/iommu/iommufd/hw_pagetable.c +3 -0
index 5be7a31cbd9c..26a8a818ffa3 100644
@@ -83,6 +83,9 @@ iommufd_hw_pagetable_alloc(struct iommufd_ctx *ictx, struct iommufd_ioas *ioas,
 
  	lockdep_assert_held(&ioas->mutex);
 
+	if ((flags & IOMMU_HWPT_ALLOC_NEST_PARENT) && !ops->domain_alloc_user)
+		return ERR_PTR(-EOPNOTSUPP);
+
  	hwpt = iommufd_object_alloc(ictx, hwpt, IOMMUFD_OBJ_HW_PAGETABLE);
  	if (IS_ERR(hwpt))
  		return hwpt;

drivers/iommu/iommufd/hw_pagetable.c int iommufd_hwpt_alloc(struct iommufd_ucmd *ucmd) · line 161

Quoted 6 lines
drivers/iommu/iommufd/hw_pagetable.c +1 -1
@@ -154,7 +157,7 @@ int iommufd_hwpt_alloc(struct iommufd_ucmd *ucmd)
  	struct iommufd_ioas *ioas;
  	int rc;
 
-	if (cmd->flags || cmd->__reserved)
+	if (cmd->flags & ~IOMMU_HWPT_ALLOC_NEST_PARENT || cmd->__reserved)
  		return -EOPNOTSUPP;

Need a parenthesis here, otherwise the compiler will interpret it as a different condition.

	if ((cmd->flags & ~IOMMU_HWPT_ALLOC_NEST_PARENT) || cmd->__reserved)
		return -EOPNOTSUPP;

Best regards,
baolu

author
#9 lore raw

Re: [PATCH 4/6] iommufd/hw_pagetable: Support allocating nested parent domain

Quoted 32 lines · Baolu Lu
Quoted 22 lines · Yi Liu

This extends IOMMU_HWPT_ALLOC to allocate domains used as parent (stage-2) in nested translation.

---
  drivers/iommu/iommufd/hw_pagetable.c | 5 ++++-

  1 file changed, 4 insertions(+), 1 deletion(-)
drivers/iommu/iommufd/hw_pagetable.c +3 -0
index 5be7a31cbd9c..26a8a818ffa3 100644
@@ -83,6 +83,9 @@ iommufd_hw_pagetable_alloc(struct iommufd_ctx *ictx, 
 struct iommufd_ioas *ioas,
       lockdep_assert_held(&ioas->mutex);
+    if ((flags & IOMMU_HWPT_ALLOC_NEST_PARENT) && !ops->domain_alloc_user)
+        return ERR_PTR(-EOPNOTSUPP);
+
       hwpt = iommufd_object_alloc(ictx, hwpt, IOMMUFD_OBJ_HW_PAGETABLE);
       if (IS_ERR(hwpt))
           return hwpt;

drivers/iommu/iommufd/hw_pagetable.c int iommufd_hwpt_alloc(struct iommufd_ucmd *ucmd) · line 160

Quoted 5 lines
drivers/iommu/iommufd/hw_pagetable.c +1 -1
@@ -154,7 +157,7 @@ int iommufd_hwpt_alloc(struct iommufd_ucmd *ucmd)
       struct iommufd_ioas *ioas;
       int rc;
-    if (cmd->flags || cmd->__reserved)
+    if (cmd->flags & ~IOMMU_HWPT_ALLOC_NEST_PARENT || cmd->__reserved)
           return -EOPNOTSUPP;

Need a parenthesis here, otherwise the compiler will interpret it as a different condition.

Quoted 2 lines

    if ((cmd->flags & ~IOMMU_HWPT_ALLOC_NEST_PARENT) || cmd->__reserved) return -EOPNOTSUPP;

ok.

Signature · 2 lines
Regards,
Yi Liu
maintainer
#10 lore raw

RE: [PATCH 4/6] iommufd/hw_pagetable: Support allocating nested parent domain

In reply to Yi Liu

drivers/iommu/iommufd/hw_pagetable.c iommufd_hw_pagetable_alloc(struct iommufd_ctx *ictx, · line 90

Quoted 12 lines

From: Liu, Yi L <[email protected]>
Sent: Tuesday, September 19, 2023 5:25 PM

drivers/iommu/iommufd/hw_pagetable.c +3 -0
@@ -83,6 +83,9 @@ iommufd_hw_pagetable_alloc(struct iommufd_ctx *ictx,
 struct iommufd_ioas *ioas,
 
 	lockdep_assert_held(&ioas->mutex);
 
+	if ((flags & IOMMU_HWPT_ALLOC_NEST_PARENT) && !ops-
 >domain_alloc_user)
+		return ERR_PTR(-EOPNOTSUPP);
+

if (flags && !ops->domain_alloc_user)

	return ERR_PTR(-EOPNOTSUPP);

as long as flags is non-zero we'll need the new alloc_user ops.

author
#11 lore raw

Re: [PATCH 4/6] iommufd/hw_pagetable: Support allocating nested parent domain

Quoted 9 lines · Kevin
Quoted 9 lines

From: Liu, Yi L <[email protected]>
Sent: Tuesday, September 19, 2023 5:25 PM

drivers/iommu/iommufd/hw_pagetable.c +1 -0
@@ -83,6 +83,9 @@ iommufd_hw_pagetable_alloc(struct iommufd_ctx *ictx,
 struct iommufd_ioas *ioas,
 
  	lockdep_assert_held(&ioas->mutex);
 
+	if ((flags & IOMMU_HWPT_ALLOC_NEST_PARENT) && !ops-
Quoted 8 lines

drivers/iommu/iommufd/hw_pagetable.c iommufd_hw_pagetable_alloc(struct iommufd_ctx *ictx, struct iommufd_ioas *ioas, · line 88

Quoted 3 lines
drivers/iommu/iommufd/hw_pagetable.c +2 -0
 > domain_alloc_user)
+		return ERR_PTR(-EOPNOTSUPP);
+

if (flags && !ops->domain_alloc_user)

	return ERR_PTR(-EOPNOTSUPP);

as long as flags is non-zero we'll need the new alloc_user ops.

yes.

Signature · 2 lines
Regards,
Yi Liu
author
#12 lore raw

PATCH 5/6 iommufd/selftest: Add domain_alloc_user() support in iommu mock

In reply to Yi Liu

This adds mock_domain_alloc_user function and also new test case for the new flag IOMMU_HWPT_ALLOC_NEST_PARENT.

---
 drivers/iommu/iommufd/selftest.c              | 16 +++++++++++++
 tools/testing/selftests/iommu/iommufd.c       | 24 +++++++++++++++----
 .../selftests/iommu/iommufd_fail_nth.c        |  2 +-
 tools/testing/selftests/iommu/iommufd_utils.h | 11 ++++++---
 4 files changed, 45 insertions(+), 8 deletions(-)
drivers/iommu/iommufd/selftest.c +16 -0
index 56506d5753f1..b54cbfb1862b 100644
@@ -146,6 +146,8 @@ static void *mock_domain_hw_info(struct device *dev, u32 *length, u32 *type)
 	return info;
 }
 
+static const struct iommu_ops mock_ops;
+
 static struct iommu_domain *mock_domain_alloc(unsigned int iommu_domain_type)
 {
 	struct mock_iommu_domain *mock;
@@ -162,10 +164,23 @@ static struct iommu_domain *mock_domain_alloc(unsigned int iommu_domain_type)
 	mock->domain.geometry.aperture_start = MOCK_APERTURE_START;
 	mock->domain.geometry.aperture_end = MOCK_APERTURE_LAST;
 	mock->domain.pgsize_bitmap = MOCK_IO_PAGE_SIZE;
+	mock->domain.ops = mock_ops.default_domain_ops;
+	mock->domain.type = iommu_domain_type;
 	xa_init(&mock->pfns);
 	return &mock->domain;
 }
 
+static struct iommu_domain *
+mock_domain_alloc_user(struct device *dev, u32 flags)
+{
+	struct iommu_domain *domain;
+
+	domain = mock_domain_alloc(IOMMU_DOMAIN_UNMANAGED);
+	if (!domain)
+		domain = ERR_PTR(-ENOMEM);
+	return domain;
+}
+
 static void mock_domain_free(struct iommu_domain *domain)
 {
 	struct mock_iommu_domain *mock =
@@ -307,6 +322,7 @@ static const struct iommu_ops mock_ops = {
 	.pgsize_bitmap = MOCK_IO_PAGE_SIZE,
 	.hw_info = mock_domain_hw_info,
 	.domain_alloc = mock_domain_alloc,
+	.domain_alloc_user = mock_domain_alloc_user,
 	.capable = mock_domain_capable,
 	.set_platform_dma_ops = mock_domain_set_plaform_dma_ops,
 	.device_group = generic_device_group,
tools/testing/selftests/iommu/iommufd.c +20 -4
index 9f705c1ea30f..9c129e63d7c7 100644
@@ -114,6 +114,7 @@ TEST_F(iommufd, cmd_length)
 
 	TEST_LENGTH(iommu_destroy, IOMMU_DESTROY);
 	TEST_LENGTH(iommu_hw_info, IOMMU_GET_HW_INFO);
+	TEST_LENGTH(iommu_hwpt_alloc, IOMMU_HWPT_ALLOC);
 	TEST_LENGTH(iommu_ioas_alloc, IOMMU_IOAS_ALLOC);
 	TEST_LENGTH(iommu_ioas_iova_ranges, IOMMU_IOAS_IOVA_RANGES);
 	TEST_LENGTH(iommu_ioas_allow_iovas, IOMMU_IOAS_ALLOW_IOVAS);
@@ -1404,13 +1405,28 @@ TEST_F(iommufd_mock_domain, alloc_hwpt)
 	int i;
 
 	for (i = 0; i != variant->mock_domains; i++) {
+		uint32_t hwpt_id[2];
 		uint32_t stddev_id;
-		uint32_t hwpt_id;
 
-		test_cmd_hwpt_alloc(self->idev_ids[i], self->ioas_id, &hwpt_id);
-		test_cmd_mock_domain(hwpt_id, &stddev_id, NULL, NULL);
+		test_err_hwpt_alloc(EOPNOTSUPP,
+				    self->idev_ids[i], self->ioas_id,
+				    ~IOMMU_HWPT_ALLOC_NEST_PARENT, &hwpt_id[0]);
+		test_cmd_hwpt_alloc(self->idev_ids[i], self->ioas_id,
+				    0, &hwpt_id[0]);
+		test_cmd_hwpt_alloc(self->idev_ids[i], self->ioas_id,
+				    IOMMU_HWPT_ALLOC_NEST_PARENT, &hwpt_id[1]);
+
+		/* Do a hw_pagetable rotation test */
+		test_cmd_mock_domain_replace(self->stdev_ids[i], hwpt_id[0]);
+		EXPECT_ERRNO(EBUSY, _test_ioctl_destroy(self->fd, hwpt_id[0]));
+		test_cmd_mock_domain_replace(self->stdev_ids[i], hwpt_id[1]);
+		EXPECT_ERRNO(EBUSY, _test_ioctl_destroy(self->fd, hwpt_id[1]));
+		test_cmd_mock_domain_replace(self->stdev_ids[i], self->ioas_id);
+		test_ioctl_destroy(hwpt_id[1]);
+
+		test_cmd_mock_domain(hwpt_id[0], &stddev_id, NULL, NULL);
 		test_ioctl_destroy(stddev_id);
-		test_ioctl_destroy(hwpt_id);
+		test_ioctl_destroy(hwpt_id[0]);
 	}
 }
 
tools/testing/selftests/iommu/iommufd_fail_nth.c +1 -1
index a220ca2a689d..3d7838506bfe 100644
@@ -615,7 +615,7 @@ TEST_FAIL_NTH(basic_fail_nth, device)
 	if (_test_cmd_get_hw_info(self->fd, idev_id, &info, sizeof(info)))
 		return -1;
 
-	if (_test_cmd_hwpt_alloc(self->fd, idev_id, ioas_id, &hwpt_id))
+	if (_test_cmd_hwpt_alloc(self->fd, idev_id, ioas_id, 0, &hwpt_id))
 		return -1;
 
 	if (_test_cmd_mock_domain_replace(self->fd, stdev_id, ioas_id2, NULL))
tools/testing/selftests/iommu/iommufd_utils.h +8 -3
index e0753d03ecaa..be4970a84977 100644
@@ -103,10 +103,11 @@ static int _test_cmd_mock_domain_replace(int fd, __u32 stdev_id, __u32 pt_id,
 							   pt_id, NULL))
 
 static int _test_cmd_hwpt_alloc(int fd, __u32 device_id, __u32 pt_id,
-					 __u32 *hwpt_id)
+				__u32 flags, __u32 *hwpt_id)
 {
 	struct iommu_hwpt_alloc cmd = {
 		.size = sizeof(cmd),
+		.flags = flags,
 		.dev_id = device_id,
 		.pt_id = pt_id,
 	};
@@ -120,8 +121,12 @@ static int _test_cmd_hwpt_alloc(int fd, __u32 device_id, __u32 pt_id,
 	return 0;
 }
 
-#define test_cmd_hwpt_alloc(device_id, pt_id, hwpt_id) \
-	ASSERT_EQ(0, _test_cmd_hwpt_alloc(self->fd, device_id, pt_id, hwpt_id))
+#define test_cmd_hwpt_alloc(device_id, pt_id, flags, hwpt_id) \
+	ASSERT_EQ(0, _test_cmd_hwpt_alloc(self->fd, device_id, \
+					  pt_id, flags, hwpt_id))
+#define test_err_hwpt_alloc(_errno, device_id, pt_id, flags, hwpt_id) \
+	EXPECT_ERRNO(_errno, _test_cmd_hwpt_alloc(self->fd, device_id, \
+						  pt_id, flags, hwpt_id))
 
 static int _test_cmd_access_replace_ioas(int fd, __u32 access_id,
 					 unsigned int ioas_id)
Signature · 1 line
2.34.1
maintainer
#13 lore raw

RE: [PATCH 5/6] iommufd/selftest: Add domain_alloc_user() support in iommu mock

drivers/iommu/iommufd/selftest.c static struct iommu_domain *mock_domain_alloc(unsigned int iommu_domain_type) · line 182

Quoted 13 lines

From: Liu, Yi L <[email protected]>
Sent: Tuesday, September 19, 2023 5:25 PM

drivers/iommu/iommufd/selftest.c +10 -0
+static struct iommu_domain *
+mock_domain_alloc_user(struct device *dev, u32 flags)
+{
+	struct iommu_domain *domain;
+
+	domain = mock_domain_alloc(IOMMU_DOMAIN_UNMANAGED);
+	if (!domain)
+		domain = ERR_PTR(-ENOMEM);
+	return domain;
+}

this also needs to validate whether the flags bits are supported.

author
#14 lore raw

PATCH 6/6 iommu/vt-d: Add domain_alloc_user op

In reply to Yi Liu

This adds the domain_alloc_user op implementation. It supports allocating domains to be used as parent under nested translation.

---
 drivers/iommu/intel/iommu.c | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)
drivers/iommu/intel/iommu.c +20 -0
index 5db283c17e0d..491bcde1ff96 100644
@@ -4074,6 +4074,25 @@ static struct iommu_domain *intel_iommu_domain_alloc(unsigned type)
 	return NULL;
 }
 
+static struct iommu_domain *
+intel_iommu_domain_alloc_user(struct device *dev, u32 flags)
+{
+	struct iommu_domain *domain;
+	struct intel_iommu *iommu;
+
+	iommu = device_to_iommu(dev, NULL, NULL);
+	if (!iommu)
+		return ERR_PTR(-ENODEV);
+
+	if ((flags & IOMMU_HWPT_ALLOC_NEST_PARENT) && !ecap_nest(iommu->ecap))
+		return ERR_PTR(-EOPNOTSUPP);
+
+	domain = iommu_domain_alloc(dev->bus);
+	if (!domain)
+		domain = ERR_PTR(-ENOMEM);
+	return domain;
+}
+
 static void intel_iommu_domain_free(struct iommu_domain *domain)
 {
 	if (domain != &si_domain->domain && domain != &blocking_domain)
@@ -4807,6 +4826,7 @@ const struct iommu_ops intel_iommu_ops = {
 	.capable		= intel_iommu_capable,
 	.hw_info		= intel_iommu_hw_info,
 	.domain_alloc		= intel_iommu_domain_alloc,
+	.domain_alloc_user	= intel_iommu_domain_alloc_user,
 	.probe_device		= intel_iommu_probe_device,
 	.probe_finalize		= intel_iommu_probe_finalize,
 	.release_device		= intel_iommu_release_device,
Signature · 1 line
2.34.1
maintainer
#15 lore raw

Re: [PATCH 6/6] iommu/vt-d: Add domain_alloc_user op

Quoted 2 lines · Yi Liu

This adds the domain_alloc_user op implementation. It supports allocating domains to be used as parent under nested translation.

Documentation/process/submitting-patches.rst:

Describe your changes in imperative mood, e.g. "make xyzzy do frotz" instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy to do frotz", as if you are giving orders to the codebase to change its behaviour.

So how about,

Add the domain_alloc_user callback to support allocating domains used as parent under nested translation.

?

Quoted 18 lines
---
  drivers/iommu/intel/iommu.c | 20 ++++++++++++++++++++
  1 file changed, 20 insertions(+)
drivers/iommu/intel/iommu.c +4 -0
index 5db283c17e0d..491bcde1ff96 100644
@@ -4074,6 +4074,25 @@ static struct iommu_domain *intel_iommu_domain_alloc(unsigned type)
  	return NULL;
  }
 
+static struct iommu_domain *
+intel_iommu_domain_alloc_user(struct device *dev, u32 flags)
+{
+	struct iommu_domain *domain;

drivers/iommu/intel/iommu.c static struct iommu_domain *intel_iommu_domain_alloc(unsigned type) · line 4090

Quoted 10 lines
drivers/iommu/intel/iommu.c +10 -0
+	struct intel_iommu *iommu;
+
+	iommu = device_to_iommu(dev, NULL, NULL);
+	if (!iommu)
+		return ERR_PTR(-ENODEV);
+
+	if ((flags & IOMMU_HWPT_ALLOC_NEST_PARENT) && !ecap_nest(iommu->ecap))
+		return ERR_PTR(-EOPNOTSUPP);
+
+	domain = iommu_domain_alloc(dev->bus);

No need to bounce between core and driver. Just,

	intel_iommu_domain_alloc(IOMMU_DOMAIN_UNMANAGED);

and fully initialize it before return.

Quoted 9 lines
drivers/iommu/intel/iommu.c +5 -0
+	if (!domain)
+		domain = ERR_PTR(-ENOMEM);
+	return domain;
+}
+
  static void intel_iommu_domain_free(struct iommu_domain *domain)
  {
  	if (domain != &si_domain->domain && domain != &blocking_domain)

drivers/iommu/intel/iommu.c const struct iommu_ops intel_iommu_ops = { · line 4832

Quoted 7 lines
drivers/iommu/intel/iommu.c +1 -0
@@ -4807,6 +4826,7 @@ const struct iommu_ops intel_iommu_ops = {
  	.capable		= intel_iommu_capable,
  	.hw_info		= intel_iommu_hw_info,
  	.domain_alloc		= intel_iommu_domain_alloc,
+	.domain_alloc_user	= intel_iommu_domain_alloc_user,
  	.probe_device		= intel_iommu_probe_device,
  	.probe_finalize		= intel_iommu_probe_finalize,
  	.release_device		= intel_iommu_release_device,

Best regards,
baolu

maintainer
#16 lore raw

Re: [PATCH 6/6] iommu/vt-d: Add domain_alloc_user op

Quoted 12 lines · Baolu Lu
Quoted 12 lines
drivers/iommu/intel/iommu.c +4 -0
index 5db283c17e0d..491bcde1ff96 100644
@@ -4074,6 +4074,25 @@ static struct iommu_domain *intel_iommu_domain_alloc(unsigned type)
  	return NULL;
  }
+static struct iommu_domain *
+intel_iommu_domain_alloc_user(struct device *dev, u32 flags)
+{
+	struct iommu_domain *domain;
Quoted 8 lines

drivers/iommu/intel/iommu.c static struct iommu_domain *intel_iommu_domain_alloc(unsigned type) · line 4088

Quoted 8 lines
drivers/iommu/intel/iommu.c +8 -0
+	struct intel_iommu *iommu;
+
+	iommu = device_to_iommu(dev, NULL, NULL);
+	if (!iommu)
+		return ERR_PTR(-ENODEV);
+
+	if ((flags & IOMMU_HWPT_ALLOC_NEST_PARENT) && !ecap_nest(iommu->ecap))
+		return ERR_PTR(-EOPNOTSUPP);

There is a check missing for supported flags

if (flags & (~IOMMU_HWPT_ALLOC_NEST_PARENT))

	return ERR_PTR(-EOPNOTSUPP);
Quoted 8 lines

drivers/iommu/intel/iommu.c static struct iommu_domain *intel_iommu_domain_alloc(unsigned type) · line 4089

Quoted 2 lines
drivers/iommu/intel/iommu.c +2 -0
+
+	domain = iommu_domain_alloc(dev->bus);

No need to bounce between core and driver. Just,

	intel_iommu_domain_alloc(IOMMU_DOMAIN_UNMANAGED);

and fully initialize it before return.

If you are going to do that then intel_iommu_domain_alloc() should fully initialize the domain, not here.

Jason

author
#17 lore raw

RE: [PATCH 6/6] iommu/vt-d: Add domain_alloc_user op

Quoted 25 lines

From: Jason Gunthorpe <[email protected]>
Sent: Wednesday, September 20, 2023 9:05 PM

Quoted 6 lines · Baolu Lu

drivers/iommu/intel/iommu.c static struct iommu_domain

Quoted 6 lines
drivers/iommu/intel/iommu.c +0 -0
index 5db283c17e0d..491bcde1ff96 100644
@@ -4074,6 +4074,25 @@ static struct iommu_domain

*intel_iommu_domain_alloc(unsigned type)

Quoted 14 lines

drivers/iommu/intel/iommu.c static struct iommu_domain *intel_iommu_domain_alloc(unsigned type)

Quoted 13 lines
drivers/iommu/intel/iommu.c +11 -0
  	return NULL;
  }
+static struct iommu_domain *
+intel_iommu_domain_alloc_user(struct device *dev, u32 flags)
+{
+	struct iommu_domain *domain;
+	struct intel_iommu *iommu;
+
+	iommu = device_to_iommu(dev, NULL, NULL);
+	if (!iommu)
+		return ERR_PTR(-ENODEV);
+
+	if ((flags & IOMMU_HWPT_ALLOC_NEST_PARENT) && !ecap_nest(iommu-

ecap))

Quoted 6 lines
Quoted 1 line

drivers/iommu/intel/iommu.c static struct iommu_domain *intel_iommu_domain_alloc(unsigned type) · line 4088

Quoted 1 line
drivers/iommu/intel/iommu.c +1 -0
+		return ERR_PTR(-EOPNOTSUPP);

There is a check missing for supported flags

if (flags & (~IOMMU_HWPT_ALLOC_NEST_PARENT))

	return ERR_PTR(-EOPNOTSUPP);

Well, the iommufd has such check. But I also noticed your another reply to Weijiang. So your preference is to do the flags validation in iommu driver instead of iommufd. Isn't it?

Quoted 11 lines
Quoted 8 lines

drivers/iommu/intel/iommu.c static struct iommu_domain · line 4089

Quoted 2 lines
drivers/iommu/intel/iommu.c +2 -0
+
+	domain = iommu_domain_alloc(dev->bus);

No need to bounce between core and driver. Just,

	intel_iommu_domain_alloc(IOMMU_DOMAIN_UNMANAGED);

and fully initialize it before return.

If you are going to do that then intel_iommu_domain_alloc() should fully initialize the domain, not here.

I've also considered what Baolu described, but it requires to do some extra initialization which is duplicated with iommu_domain_alloc(). So I chose this simple way.

Regards,
Yi Liu

maintainer
#18 lore raw

Re: [PATCH 6/6] iommu/vt-d: Add domain_alloc_user op

Quoted 29 lines · Yi L
Quoted 29 lines

From: Jason Gunthorpe <[email protected]>
Sent: Wednesday, September 20, 2023 9:05 PM

Quoted 6 lines · Baolu Lu

drivers/iommu/intel/iommu.c static struct iommu_domain

Quoted 6 lines
drivers/iommu/intel/iommu.c +0 -0
index 5db283c17e0d..491bcde1ff96 100644
@@ -4074,6 +4074,25 @@ static struct iommu_domain

*intel_iommu_domain_alloc(unsigned type)

Quoted 14 lines

drivers/iommu/intel/iommu.c static struct iommu_domain *intel_iommu_domain_alloc(unsigned type)

Quoted 13 lines
drivers/iommu/intel/iommu.c +11 -0
  	return NULL;
  }
+static struct iommu_domain *
+intel_iommu_domain_alloc_user(struct device *dev, u32 flags)
+{
+	struct iommu_domain *domain;
+	struct intel_iommu *iommu;
+
+	iommu = device_to_iommu(dev, NULL, NULL);
+	if (!iommu)
+		return ERR_PTR(-ENODEV);
+
+	if ((flags & IOMMU_HWPT_ALLOC_NEST_PARENT) && !ecap_nest(iommu-

ecap))

Quoted 1 line

drivers/iommu/intel/iommu.c static struct iommu_domain *intel_iommu_domain_alloc(unsigned type) · line 4088

Quoted 1 line
drivers/iommu/intel/iommu.c +1 -0
+		return ERR_PTR(-EOPNOTSUPP);

There is a check missing for supported flags

Quoted 6 lines
Quoted 2 lines

if (flags & (~IOMMU_HWPT_ALLOC_NEST_PARENT))

	return ERR_PTR(-EOPNOTSUPP);

Well, the iommufd has such check. But I also noticed your another reply to Weijiang. So your preference is to do the flags validation in iommu driver instead of iommufd. Isn't it?

The core code should check that only kernel known bits are set

The driver code should check that only driver supported bits are set.

Today there is only one bit so the checks are the same code.

Tomorrow when we add a new bit the checks will not be the same

Jason

author
#19 lore raw

Re: [PATCH 6/6] iommu/vt-d: Add domain_alloc_user op

Quoted 37 lines · Jason Gunthorpe
Quoted 29 lines · Yi L
Quoted 29 lines

From: Jason Gunthorpe <[email protected]>
Sent: Wednesday, September 20, 2023 9:05 PM

Quoted 6 lines · Baolu Lu

drivers/iommu/intel/iommu.c static struct iommu_domain

Quoted 6 lines
drivers/iommu/intel/iommu.c +0 -0
index 5db283c17e0d..491bcde1ff96 100644
@@ -4074,6 +4074,25 @@ static struct iommu_domain

*intel_iommu_domain_alloc(unsigned type)

Quoted 14 lines

drivers/iommu/intel/iommu.c static struct iommu_domain *intel_iommu_domain_alloc(unsigned type)

Quoted 13 lines
drivers/iommu/intel/iommu.c +11 -0
   	return NULL;
   }
+static struct iommu_domain *
+intel_iommu_domain_alloc_user(struct device *dev, u32 flags)
+{
+	struct iommu_domain *domain;
+	struct intel_iommu *iommu;
+
+	iommu = device_to_iommu(dev, NULL, NULL);
+	if (!iommu)
+		return ERR_PTR(-ENODEV);
+
+	if ((flags & IOMMU_HWPT_ALLOC_NEST_PARENT) && !ecap_nest(iommu-

ecap))

Quoted 1 line

drivers/iommu/intel/iommu.c static struct iommu_domain *intel_iommu_domain_alloc(unsigned type) · line 4088

Quoted 1 line
drivers/iommu/intel/iommu.c +1 -0
+		return ERR_PTR(-EOPNOTSUPP);

There is a check missing for supported flags

Quoted 6 lines
Quoted 2 lines

if (flags & (~IOMMU_HWPT_ALLOC_NEST_PARENT))

	return ERR_PTR(-EOPNOTSUPP);

Well, the iommufd has such check. But I also noticed your another reply to Weijiang. So your preference is to do the flags validation in iommu driver instead of iommufd. Isn't it?

Quoted 7 lines

The core code should check that only kernel known bits are set

The driver code should check that only driver supported bits are set.

Today there is only one bit so the checks are the same code.

Tomorrow when we add a new bit the checks will not be the same

fair enough. I'll have the check in both core and iommu driver.

if (flags & (~IOMMU_HWPT_ALLOC_NEST_PARENT))
return ERR_PTR(-EOPNOTSUPP);

Signature · 2 lines
Regards,
Yi Liu
maintainer
#20 lore raw

Re: [PATCH 6/6] iommu/vt-d: Add domain_alloc_user op

In reply to Liu, Yi L
Quoted 4 lines · Yi L
Quoted 4 lines
Quoted 4 lines

Review

Quoted 2 lines
(quoted diff) +2 -0
+
+	domain = iommu_domain_alloc(dev->bus);

No need to bounce between core and driver. Just,

Quoted 8 lines
Quoted 5 lines
Quoted 3 lines
	intel_iommu_domain_alloc(IOMMU_DOMAIN_UNMANAGED);

and fully initialize it before return.

If you are going to do that then intel_iommu_domain_alloc() should fully initialize the domain, not here.

I've also considered what Baolu described, but it requires to do some extra initialization which is duplicated with iommu_domain_alloc(). So I chose this simple way.

Okay, got you.

Once Jason's paging domain and Robin's bus->iommu_ops retirement series have landed, the VT-d driver will need some refactoring. Therefore, I'm fine with you using a simpler approach here. I'll refactor everything later.

Best regards,
baolu

author
#21 lore raw

Re: [PATCH 6/6] iommu/vt-d: Add domain_alloc_user op

Quoted 14 lines · Baolu Lu
Quoted 4 lines · Yi L
Quoted 4 lines
Quoted 4 lines
Quoted 2 lines

+
+    domain = iommu_domain_alloc(dev->bus);

No need to bounce between core and driver. Just,

Quoted 8 lines
Quoted 5 lines
Quoted 3 lines

    intel_iommu_domain_alloc(IOMMU_DOMAIN_UNMANAGED);

and fully initialize it before return.

If you are going to do that then intel_iommu_domain_alloc() should fully initialize the domain, not here.

I've also considered what Baolu described, but it requires to do some extra initialization which is duplicated with iommu_domain_alloc(). So I chose this simple way.

Quoted 6 lines

Okay, got you.

Once Jason's paging domain and Robin's bus->iommu_ops retirement series have landed, the VT-d driver will need some refactoring. Therefore, I'm fine with you using a simpler approach here. I'll refactor everything later.

yes.

Signature · 2 lines
Regards,
Yi Liu
maintainer
#22 lore raw

RE: [PATCH 6/6] iommu/vt-d: Add domain_alloc_user op

In reply to Baolu Lu
Quoted 10 lines

From: Baolu Lu <[email protected]>
Sent: Thursday, September 21, 2023 9:31 AM

Quoted 6 lines · Yi L
Quoted 6 lines
Quoted 6 lines

Review

Quoted 2 lines
(quoted diff) +2 -0
+
+	domain = iommu_domain_alloc(dev->bus);

No need to bounce between core and driver. Just,

	intel_iommu_domain_alloc(IOMMU_DOMAIN_UNMANAGED);
Quoted 9 lines
Quoted 6 lines
Quoted 3 lines
Quoted 1 line

and fully initialize it before return.

If you are going to do that then intel_iommu_domain_alloc() should fully initialize the domain, not here.

I've also considered what Baolu described, but it requires to do some extra initialization which is duplicated with iommu_domain_alloc(). So I chose this simple way.

Okay, got you.

Please add a comment for this temporary option.

author
#23 lore raw

RE: [PATCH 6/6] iommu/vt-d: Add domain_alloc_user op

In reply to Baolu Lu
Quoted 14 lines

From: Baolu Lu <[email protected]>
Sent: Wednesday, September 20, 2023 1:29 PM

Quoted 2 lines · Yi Liu

This adds the domain_alloc_user op implementation. It supports allocating domains to be used as parent under nested translation.

Documentation/process/submitting-patches.rst:

Describe your changes in imperative mood, e.g. "make xyzzy do frotz" instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy to do frotz", as if you are giving orders to the codebase to change its behaviour.

Quoted 5 lines

So how about,

Add the domain_alloc_user callback to support allocating domains used as parent under nested translation.

Sure.

#24 lore raw

Re: [PATCH 6/6] iommu/vt-d: Add domain_alloc_user op

In reply to Yi Liu
Quoted 18 lines · Yi Liu

This adds the domain_alloc_user op implementation. It supports allocating domains to be used as parent under nested translation.

---
  drivers/iommu/intel/iommu.c | 20 ++++++++++++++++++++
  1 file changed, 20 insertions(+)
drivers/iommu/intel/iommu.c +2 -0
index 5db283c17e0d..491bcde1ff96 100644
@@ -4074,6 +4074,25 @@ static struct iommu_domain *intel_iommu_domain_alloc(unsigned type)
  	return NULL;
  }
 
+static struct iommu_domain *
+intel_iommu_domain_alloc_user(struct device *dev, u32 flags)

drivers/iommu/intel/iommu.c static struct iommu_domain *intel_iommu_domain_alloc(unsigned type) · line 4088

Quoted 10 lines
drivers/iommu/intel/iommu.c +10 -0
+{
+	struct iommu_domain *domain;
+	struct intel_iommu *iommu;
+
+	iommu = device_to_iommu(dev, NULL, NULL);
+	if (!iommu)
+		return ERR_PTR(-ENODEV);
+
+	if ((flags & IOMMU_HWPT_ALLOC_NEST_PARENT) && !ecap_nest(iommu->ecap))
+		return ERR_PTR(-EOPNOTSUPP);

The outer caller has checked (flags & IOMMU_HWPT_ALLOC_NEST_PARENT) before it comes here. If this callback is dedicated for nested domain allocation, then you may omit the condition here.

maintainer
#25 lore raw

Re: [PATCH 6/6] iommu/vt-d: Add domain_alloc_user op

Quoted 23 lines · Weijiang
Quoted 22 lines · Yi Liu

This adds the domain_alloc_user op implementation. It supports allocating domains to be used as parent under nested translation.

---
  drivers/iommu/intel/iommu.c | 20 ++++++++++++++++++++
  1 file changed, 20 insertions(+)
drivers/iommu/intel/iommu.c +7 -0
index 5db283c17e0d..491bcde1ff96 100644
@@ -4074,6 +4074,25 @@ static struct iommu_domain *intel_iommu_domain_alloc(unsigned type)
  	return NULL;
  }
+static struct iommu_domain *
+intel_iommu_domain_alloc_user(struct device *dev, u32 flags)
+{
+	struct iommu_domain *domain;
+	struct intel_iommu *iommu;
+
+	iommu = device_to_iommu(dev, NULL, NULL);
Quoted 8 lines

drivers/iommu/intel/iommu.c static struct iommu_domain *intel_iommu_domain_alloc(unsigned type) · line 4088

Quoted 5 lines
drivers/iommu/intel/iommu.c +5 -0
+	if (!iommu)
+		return ERR_PTR(-ENODEV);
+
+	if ((flags & IOMMU_HWPT_ALLOC_NEST_PARENT) && !ecap_nest(iommu->ecap))
+		return ERR_PTR(-EOPNOTSUPP);

The outer caller has checked (flags & IOMMU_HWPT_ALLOC_NEST_PARENT) before it comes here. If this callback is dedicated for nested domain allocation, then you may omit the condition here.

No, please don't.

The point of the flags is to be passed to the driver. The driver should validate them, not the core code.

We will add more flags, I don't want to change every driver to do this.

Jason

author
#26 lore raw

RE: [PATCH 6/6] iommu/vt-d: Add domain_alloc_user op

In reply to Yang, Weijiang
Quoted 30 lines

From: Yang, Weijiang <[email protected]>
Sent: Wednesday, September 20, 2023 1:41 PM

drivers/iommu/intel/iommu.c static struct iommu_domain

Quoted 13 lines · Yi Liu

This adds the domain_alloc_user op implementation. It supports allocating domains to be used as parent under nested translation.

---
  drivers/iommu/intel/iommu.c | 20 ++++++++++++++++++++
  1 file changed, 20 insertions(+)
drivers/iommu/intel/iommu.c +0 -0
index 5db283c17e0d..491bcde1ff96 100644
@@ -4074,6 +4074,25 @@ static struct iommu_domain

*intel_iommu_domain_alloc(unsigned type)

Quoted 13 lines
drivers/iommu/intel/iommu.c +10 -0
  	return NULL;
  }
 
+static struct iommu_domain *
+intel_iommu_domain_alloc_user(struct device *dev, u32 flags)
+{
+	struct iommu_domain *domain;
+	struct intel_iommu *iommu;
+
+	iommu = device_to_iommu(dev, NULL, NULL);
+	if (!iommu)
+		return ERR_PTR(-ENODEV);
+
Quoted 8 lines

drivers/iommu/intel/iommu.c static struct iommu_domain · line 4089

Quoted 3 lines
drivers/iommu/intel/iommu.c +2 -0
+	if ((flags & IOMMU_HWPT_ALLOC_NEST_PARENT) && !ecap_nest(iommu-
 ecap))
+		return ERR_PTR(-EOPNOTSUPP);

The outer caller has checked (flags & IOMMU_HWPT_ALLOC_NEST_PARENT) before it comes here.
If this callback is dedicated for nested domain allocation, then you may omit the condition here.

This check is different. It aims to fail the call if iommu hw does not support nested. I just realized that it may need to check if scalable mode is enabled. This should be more accurate.

Regards,
Yi Liu