From: Baolu Lu <baolu.lu@linux.intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>,
David Woodhouse <dwmw2@infradead.org>,
iommu@lists.linux.dev, Joerg Roedel <joro@8bytes.org>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Will Deacon <will@kernel.org>
Cc: baolu.lu@linux.intel.com, Kevin Tian <kevin.tian@intel.com>,
Nicolin Chen <nicolinc@nvidia.com>
Subject: Re: [PATCH v2 05/10] iommu: Add iommu_init/deinit_device() paired functions
Date: Sun, 21 May 2023 19:31:38 +0800 [thread overview]
Message-ID: <5bcb5f03-77c9-116e-c436-9d0af21fa82a@linux.intel.com> (raw)
In-Reply-To: <5-v2-3c3bb7aa6e48+1916b-iommu_probe_jgg@nvidia.com>
I revisited this patch. And I still have some questions.
On 5/20/23 2:42 AM, Jason Gunthorpe wrote:
> -/*
> - * Remove the iommu_group from the struct device. The attached group must be put
> - * by the caller after releaseing the group->mutex.
> - */
> +/* Remove the iommu_group from the struct device. */
> static void __iommu_group_remove_device(struct device *dev)
> {
> struct iommu_group *group = dev->iommu_group;
> struct group_device *device;
>
> + mutex_lock(&group->mutex);
> lockdep_assert_held(&group->mutex);
By moving mutex_lock/unlock into this helper, above
lockdep_assert_held() is unnecessary.
> for_each_group_device(group, device) {
> if (device->dev != dev)
> @@ -510,44 +564,30 @@ static void __iommu_group_remove_device(struct device *dev)
>
> list_del(&device->list);
> __iommu_group_free_device(group, device);
> - /* Caller must put iommu_group */
> - return;
> + if (dev->iommu && dev->iommu->iommu_dev)
> + iommu_deinit_device(dev);
> + else
> + dev->iommu_group = NULL;
> + goto out;
> }
> WARN(true, "Corrupted iommu_group device_list");
> +out:
> + mutex_unlock(&group->mutex);
> +
> + /* Pairs with the get in iommu_group_add_device() */
> + iommu_group_put(group);
The group->devices_kobj was increased on the probe device path twice:
- iommu_init_device() - allocate the group
- iommu_group_add_device() - add device to the group
But, on the release path, it seems that group->devices_kobj is only
decreased once.
Did I overlook anything? Otherwise, the group will never be released,
right?
> }
>
> static void iommu_release_device(struct device *dev)
> {
> struct iommu_group *group = dev->iommu_group;
> - const struct iommu_ops *ops;
>
> if (!dev->iommu || !group)
> return;
>
> iommu_device_unlink(dev->iommu->iommu_dev, dev);
>
> - mutex_lock(&group->mutex);
> __iommu_group_remove_device(dev);
> -
> - /*
> - * release_device() must stop using any attached domain on the device.
> - * If there are still other devices in the group they are not effected
> - * by this callback.
> - *
> - * The IOMMU driver must set the device to either an identity or
> - * blocking translation and stop using any domain pointer, as it is
> - * going to be freed.
> - */
> - ops = dev_iommu_ops(dev);
> - if (ops->release_device)
> - ops->release_device(dev);
> - mutex_unlock(&group->mutex);
> -
> - /* Pairs with the get in iommu_group_add_device() */
> - iommu_group_put(group);
> -
> - module_put(ops->owner);
> - dev_iommu_free(dev);
> }
Best regards,
baolu
next prev parent reply other threads:[~2023-05-21 11:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 18:42 [PATCH v2 00/10] Consolidate the probe_device path Jason Gunthorpe
2023-05-19 18:42 ` [PATCH v2 01/10] iommu: Have __iommu_probe_device() check for already probed devices Jason Gunthorpe
2023-05-21 8:17 ` Baolu Lu
2023-05-22 12:18 ` Rafael J. Wysocki
2023-05-19 18:42 ` [PATCH v2 02/10] iommu: Use iommu_group_ref_get/put() for dev->iommu_group Jason Gunthorpe
2023-05-21 8:18 ` Baolu Lu
2023-05-19 18:42 ` [PATCH v2 03/10] iommu: Inline iommu_group_get_for_dev() into __iommu_probe_device() Jason Gunthorpe
2023-05-21 8:19 ` Baolu Lu
2023-06-02 17:17 ` Jason Gunthorpe
2023-05-19 18:42 ` [PATCH v2 04/10] iommu: Simplify the __iommu_group_remove_device() flow Jason Gunthorpe
2023-05-21 9:08 ` Baolu Lu
2023-05-22 8:35 ` Niklas Schnelle
2023-05-29 19:33 ` Jason Gunthorpe
2023-05-19 18:42 ` [PATCH v2 05/10] iommu: Add iommu_init/deinit_device() paired functions Jason Gunthorpe
2023-05-21 11:09 ` Baolu Lu
2023-05-21 11:31 ` Baolu Lu [this message]
2023-05-22 2:31 ` Baolu Lu
2023-06-02 17:20 ` Jason Gunthorpe
2023-05-19 18:42 ` [PATCH v2 06/10] iommu: Move the iommu driver sysfs setup into iommu_init/deinit_device() Jason Gunthorpe
2023-05-22 0:51 ` Baolu Lu
2023-05-19 18:42 ` [PATCH v2 07/10] iommu: Do not export iommu_device_link/unlink() Jason Gunthorpe
2023-05-22 0:52 ` Baolu Lu
2023-05-19 18:42 ` [PATCH v2 08/10] iommu: Always destroy the iommu_group during iommu_release_device() Jason Gunthorpe
2023-05-22 1:43 ` Baolu Lu
2023-05-19 18:42 ` [PATCH v2 09/10] iommu: Split iommu_group_add_device() Jason Gunthorpe
2023-05-22 2:34 ` Baolu Lu
2023-05-25 5:37 ` Tian, Kevin
2023-05-19 18:42 ` [PATCH v2 10/10] iommu: Avoid locking/unlocking for iommu_probe_device() Jason Gunthorpe
2023-05-22 2:39 ` Baolu Lu
2023-05-25 5:37 ` Tian, Kevin
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=5bcb5f03-77c9-116e-c436-9d0af21fa82a@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=rafael@kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
/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