From: tina.zhang <tina.zhang@intel.com>
To: Lu Baolu <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>,
Kevin Tian <kevin.tian@intel.com>,
"Jean-Philippe Brucker" <jean-philippe@linaro.org>,
Nicolin Chen <nicolinc@nvidia.com>
Cc: Yi Liu <yi.l.liu@intel.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
<iommu@lists.linux.dev>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] iommu: Move pasid array from group to device
Date: Tue, 1 Aug 2023 16:07:47 +0800 [thread overview]
Message-ID: <1254d61b-1f4e-2ef3-c3dc-95180f26f08c@intel.com> (raw)
In-Reply-To: <20230801063125.34995-3-baolu.lu@linux.intel.com>
Hi Baolu,
Although this patch moves the domain reference pointer from a per-group
structure to a per-device structure, the domain life-cycle is still
expected to be managed per-group (i.e., iommu_domain_free() is called in
iommu_group_release()). Is this what we expect?
Regards,
-Tina
On 8/1/23 14:31, Lu Baolu wrote:
> The PASID (Process Address Space ID) feature is a device feature that
> allows a device driver to manage the PASID value and attach or detach
> its domain to the pasid. The pasid array, which is used to store the
> domain of each pasid, is currently stored in iommu group struct, but
> it would be more natural to move it to the device so that the device
> drivers don't need to understand the internal iommu group concept.
>
> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
> ---
> include/linux/iommu.h | 2 ++
> drivers/iommu/iommu.c | 80 ++++++++++++-------------------------------
> 2 files changed, 24 insertions(+), 58 deletions(-)
>
> diff --git a/include/linux/iommu.h b/include/linux/iommu.h
> index b1dcb1b9b170..90be3efd0e91 100644
> --- a/include/linux/iommu.h
> +++ b/include/linux/iommu.h
> @@ -406,6 +406,7 @@ struct iommu_fault_param {
> * @iopf_param: I/O Page Fault queue and data
> * @fwspec: IOMMU fwspec data
> * @iommu_dev: IOMMU device this device is linked to
> + * @pasid_array: pasid-indexed array of domains attached to pasid
> * @priv: IOMMU Driver private data
> * @max_pasids: number of PASIDs this device can consume
> * @attach_deferred: the dma domain attachment is deferred
> @@ -420,6 +421,7 @@ struct dev_iommu {
> struct iopf_device_param *iopf_param;
> struct iommu_fwspec *fwspec;
> struct iommu_device *iommu_dev;
> + struct xarray pasid_array;
> void *priv;
> u32 max_pasids;
> u32 attach_deferred:1;
> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
> index 1a8fb30341e6..7fd53b9e9754 100644
> --- a/drivers/iommu/iommu.c
> +++ b/drivers/iommu/iommu.c
> @@ -48,7 +48,6 @@ struct iommu_group {
> struct kobject kobj;
> struct kobject *devices_kobj;
> struct list_head devices;
> - struct xarray pasid_array;
> struct mutex mutex;
> void *iommu_data;
> void (*iommu_data_release)(void *iommu_data);
> @@ -302,6 +301,7 @@ static struct dev_iommu *dev_iommu_get(struct device *dev)
> return NULL;
>
> mutex_init(¶m->lock);
> + xa_init(¶m->pasid_array);
> dev->iommu = param;
> return param;
> }
> @@ -891,7 +891,6 @@ struct iommu_group *iommu_group_alloc(void)
> mutex_init(&group->mutex);
> INIT_LIST_HEAD(&group->devices);
> INIT_LIST_HEAD(&group->entry);
> - xa_init(&group->pasid_array);
>
> ret = ida_alloc(&iommu_group_ida, GFP_KERNEL);
> if (ret < 0) {
> @@ -3041,8 +3040,11 @@ static bool iommu_is_default_domain(struct iommu_group *group)
> */
> static void assert_pasid_dma_ownership(struct iommu_group *group)
> {
> + struct group_device *device;
> +
> lockdep_assert_held(&group->mutex);
> - WARN_ON(!xa_empty(&group->pasid_array));
> + for_each_group_device(group, device)
> + WARN_ON(!xa_empty(&device->dev->iommu->pasid_array));
> }
>
> /**
> @@ -3281,33 +3283,6 @@ bool iommu_group_dma_owner_claimed(struct iommu_group *group)
> }
> EXPORT_SYMBOL_GPL(iommu_group_dma_owner_claimed);
>
> -static int __iommu_set_group_pasid(struct iommu_domain *domain,
> - struct iommu_group *group, ioasid_t pasid)
> -{
> - struct group_device *device;
> - int ret = 0;
> -
> - for_each_group_device(group, device) {
> - ret = domain->ops->set_dev_pasid(domain, device->dev, pasid);
> - if (ret)
> - break;
> - }
> -
> - return ret;
> -}
> -
> -static void __iommu_remove_group_pasid(struct iommu_group *group,
> - ioasid_t pasid)
> -{
> - struct group_device *device;
> - const struct iommu_ops *ops;
> -
> - for_each_group_device(group, device) {
> - ops = dev_iommu_ops(device->dev);
> - ops->remove_dev_pasid(device->dev, pasid);
> - }
> -}
> -
> /*
> * iommu_attach_device_pasid() - Attach a domain to pasid of device
> * @domain: the iommu domain.
> @@ -3319,32 +3294,28 @@ static void __iommu_remove_group_pasid(struct iommu_group *group,
> int iommu_attach_device_pasid(struct iommu_domain *domain,
> struct device *dev, ioasid_t pasid)
> {
> - struct iommu_group *group;
> + struct dev_iommu *param = dev->iommu;
> void *curr;
> int ret;
>
> if (!domain->ops->set_dev_pasid)
> return -EOPNOTSUPP;
>
> - group = iommu_group_get(dev);
> - if (!group)
> + if (!param)
> return -ENODEV;
>
> - mutex_lock(&group->mutex);
> - curr = xa_cmpxchg(&group->pasid_array, pasid, NULL, domain, GFP_KERNEL);
> + mutex_lock(¶m->lock);
> + curr = xa_cmpxchg(¶m->pasid_array, pasid, NULL, domain, GFP_KERNEL);
> if (curr) {
> ret = xa_err(curr) ? : -EBUSY;
> goto out_unlock;
> }
>
> - ret = __iommu_set_group_pasid(domain, group, pasid);
> - if (ret) {
> - __iommu_remove_group_pasid(group, pasid);
> - xa_erase(&group->pasid_array, pasid);
> - }
> + ret = domain->ops->set_dev_pasid(domain, dev, pasid);
> + if (ret)
> + xa_erase(¶m->pasid_array, pasid);
> out_unlock:
> - mutex_unlock(&group->mutex);
> - iommu_group_put(group);
> + mutex_unlock(¶m->lock);
>
> return ret;
> }
> @@ -3362,14 +3333,13 @@ EXPORT_SYMBOL_GPL(iommu_attach_device_pasid);
> void iommu_detach_device_pasid(struct iommu_domain *domain, struct device *dev,
> ioasid_t pasid)
> {
> - struct iommu_group *group = iommu_group_get(dev);
> + const struct iommu_ops *ops = dev_iommu_ops(dev);
> + struct dev_iommu *param = dev->iommu;
>
> - mutex_lock(&group->mutex);
> - __iommu_remove_group_pasid(group, pasid);
> - WARN_ON(xa_erase(&group->pasid_array, pasid) != domain);
> - mutex_unlock(&group->mutex);
> -
> - iommu_group_put(group);
> + mutex_lock(¶m->lock);
> + ops->remove_dev_pasid(dev, pasid);
> + WARN_ON(xa_erase(¶m->pasid_array, pasid) != domain);
> + mutex_unlock(¶m->lock);
> }
> EXPORT_SYMBOL_GPL(iommu_detach_device_pasid);
>
> @@ -3392,18 +3362,12 @@ struct iommu_domain *iommu_get_domain_for_dev_pasid(struct device *dev,
> unsigned int type)
> {
> struct iommu_domain *domain;
> - struct iommu_group *group;
>
> - group = iommu_group_get(dev);
> - if (!group)
> - return NULL;
> -
> - xa_lock(&group->pasid_array);
> - domain = xa_load(&group->pasid_array, pasid);
> + xa_lock(&dev->iommu->pasid_array);
> + domain = xa_load(&dev->iommu->pasid_array, pasid);
> if (type && domain && domain->type != type)
> domain = ERR_PTR(-EBUSY);
> - xa_unlock(&group->pasid_array);
> - iommu_group_put(group);
> + xa_unlock(&dev->iommu->pasid_array);
>
> return domain;
> }
next prev parent reply other threads:[~2023-08-01 8:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 6:31 [PATCH 0/2] iommu: Make pasid array per device Lu Baolu
2023-08-01 6:31 ` [PATCH 1/2] iommu: Consolidate pasid dma ownership check Lu Baolu
2023-08-01 7:03 ` Tian, Kevin
2023-08-01 7:43 ` Baolu Lu
2023-08-01 8:16 ` tina.zhang
2023-08-02 1:39 ` Tian, Kevin
2023-08-02 3:20 ` Baolu Lu
2023-08-01 6:31 ` [PATCH 2/2] iommu: Move pasid array from group to device Lu Baolu
2023-08-01 8:07 ` tina.zhang [this message]
2023-08-01 8:40 ` Baolu Lu
2023-08-02 14:15 ` [PATCH 0/2] iommu: Make pasid array per device Jason Gunthorpe
2023-08-03 0:44 ` Tian, Kevin
2023-08-03 15:18 ` Jason Gunthorpe
2023-08-04 0:57 ` Tian, Kevin
2023-08-04 2:20 ` Baolu Lu
2023-08-04 2:30 ` Baolu Lu
2023-08-04 13:12 ` Jason Gunthorpe
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=1254d61b-1f4e-2ef3-c3dc-95180f26f08c@intel.com \
--to=tina.zhang@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jean-philippe@linaro.org \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=yi.l.liu@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