From: Baolu Lu <baolu.lu@linux.intel.com>
To: Samiullah Khawaja <skhawaja@google.com>
Cc: baolu.lu@linux.intel.com, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>, Jason Gunthorpe <jgg@ziepe.ca>,
David Woodhouse <dwmw2@infradead.org>,
Robin Murphy <robin.murphy@arm.com>,
Kevin Tian <kevin.tian@intel.com>,
Alex Williamson <alex@shazbot.org>, Shuah Khan <shuah@kernel.org>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, Pratyush Yadav <pratyush@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
David Matlack <dmatlack@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Pranjal Shrivastava <praan@google.com>,
Vipin Sharma <vipinsh@google.com>,
Ankit Soni <Ankit.Soni@amd.com>,
Nicolin Chen <nicolinc@nvidia.com>, John Starks <dev@jstarks.net>
Subject: Re: [PATCH v6 05/18] iommu: Implement device and IOMMU HW preservation
Date: Sat, 31 Oct 2026 13:34:00 +0800 [thread overview]
Message-ID: <38384919-f0e5-4c93-b71b-065b96a74c38@linux.intel.com> (raw)
In-Reply-To: <auTzN4NWuKsBvIZU@google.com>
On 10/31/2026 9:45 AM, Samiullah Khawaja wrote:
> On Fri, Oct 30, 2026 at 01:12:31PM +0800, Baolu Lu wrote:
>> On 10/25/2026 10:19 AM, Samiullah Khawaja wrote:
>>> Add IOMMU ops to preserve/unpreserve the device state handled by the
>>> IOMMU driver. This is IOMMU specific state of the device that needs to
>>> be preserved for liveupdate. These ops can be implemented by the IOMMU
>>> drivers that support preservation of devices that have their IOMMU
>>> domains preserved. During device preservation the state of the
>>> associated IOMMU is also preserved as dependency.
>>>
>>> Signed-off-by: Samiullah Khawaja <skhawaja@google.com>
>>> ---
>>> drivers/iommu/iommu-priv.h | 2 +
>>> drivers/iommu/iommu.c | 72 +++++++++++-
>>> drivers/iommu/liveupdate.c | 189 +++++++++++++++++++++++++++++++
>>> include/linux/iommu-liveupdate.h | 76 +++++++++++++
>>> include/linux/iommu.h | 33 ++++++
>>> 5 files changed, 371 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/iommu/iommu-priv.h b/drivers/iommu/iommu-priv.h
>>> index 1f9f886b2c10..6b0ef210b32f 100644
>>> --- a/drivers/iommu/iommu-priv.h
>>> +++ b/drivers/iommu/iommu-priv.h
>>> @@ -21,6 +21,8 @@ static inline const struct iommu_ops
>>> *dev_iommu_ops(struct device *dev)
>>> void dev_iommu_free(struct device *dev);
>>> +bool iommu_group_is_singleton(struct iommu_group *group);
>>> +
>>> const struct iommu_ops *iommu_ops_from_fwnode(const struct
>>> fwnode_handle *fwnode);
>>> static inline const struct iommu_ops *iommu_fwspec_ops(struct
>>> iommu_fwspec *fwspec)
>>> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
>>> index b486b8bbd1fc..a66363789ca9 100644
>>> --- a/drivers/iommu/iommu.c
>>> +++ b/drivers/iommu/iommu.c
>>> @@ -18,6 +18,7 @@
>>> #include <linux/errno.h>
>>> #include <linux/host1x_context_bus.h>
>>> #include <linux/iommu.h>
>>> +#include <linux/iommu-liveupdate.h>
>>> #include <linux/iommufd.h>
>>> #include <linux/idr.h>
>>> #include <linux/err.h>
>>> @@ -328,6 +329,47 @@ void iommu_device_unregister(struct iommu_device
>>> *iommu)
>>> }
>>> EXPORT_SYMBOL_GPL(iommu_device_unregister);
>>> +struct iommu_dev_iter {
>>> + struct iommu_device *iommu;
>>> + iommu_dev_iter_fn fn;
>>> +};
>>> +
>>> +static int _iommu_for_each_dev_cb(struct device *dev, void *data)
>>> +{
>>> + struct iommu_dev_iter *iter = data;
>>> +
>>> + if (dev->iommu && dev->iommu->iommu_dev == iter->iommu)
>>> + return iter->fn(dev, iter->iommu);
>>> +
>>> + return 0;
>>> +}
>>> +
>>> +/**
>>> + * iommu_for_each_dev() - Iterate over all devices attached to an IOMMU
>>> + * @iommu: IOMMU instance
>>> + * @fn: Callback to call for each device attached to @iommu
>>> + *
>>> + * Return: 0 on success, or negative error code.
>>> + */
>>> +int iommu_for_each_dev(struct iommu_device *iommu, iommu_dev_iter_fn
>>> fn)
>>> +{
>>> + struct iommu_dev_iter iter = {
>>> + .iommu = iommu,
>>> + .fn = fn,
>>> + };
>>> + int ret;
>>> +
>>> + for (int i = 0; i < ARRAY_SIZE(iommu_buses); i++) {
>>> + ret = bus_for_each_dev(iommu_buses[i], NULL, &iter,
>>> + _iommu_for_each_dev_cb);
>>> + if (ret)
>>> + return ret;
>>> + }
>>> +
>>> + return 0;
>>> +}
>>> +EXPORT_SYMBOL_GPL(iommu_for_each_dev);
>>
>> The function has no locking against iommu probe or release, so the
>> callback can read dev->iommu while it is being freed or before it is
>> fully set up.
>
> It is only called from intel_iommu_shutdown(), which runs after the
> other CPUs are stopped and interrupts are disabled, so probe and release
> can't run. I will rename it to iommu_for_each_dev_unsafe(), document
> that it must only be called at shutdown and drop the export, since the
> only user is built in.
If it's only intended for the intel iommu driver, then it should be
open-coded there. There is no need to add an immature interface like
this to the core. It could be misused in the future.
Thanks,
baolu
next prev parent reply other threads:[~2026-10-31 5:34 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 2:19 [PATCH v6 00/18] iommu: Add live update state preservation Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 01/18] iommu: Implement IOMMU Live update FLB callbacks Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 02/18] iommu/pages: Add APIs to preserve/unpreserve/restore iommu pages Samiullah Khawaja
2026-10-30 1:26 ` Baolu Lu
2026-10-30 19:41 ` Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 03/18] iommupt: Implement preserve/unpreserve/restore callbacks Samiullah Khawaja
2026-10-30 3:07 ` Baolu Lu
2026-10-30 19:42 ` Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 04/18] iommu: Implement IOMMU domain preservation Samiullah Khawaja
2026-10-30 4:24 ` Baolu Lu
2026-10-25 2:19 ` [PATCH v6 05/18] iommu: Implement device and IOMMU HW preservation Samiullah Khawaja
2026-10-30 5:12 ` Baolu Lu
2026-10-31 1:45 ` Samiullah Khawaja
2026-10-31 3:04 ` Baolu Lu
2026-10-31 3:39 ` Samiullah Khawaja
2026-10-31 5:27 ` Baolu Lu
2026-10-31 5:34 ` Baolu Lu [this message]
2026-10-25 2:19 ` [PATCH v6 06/18] iommu/vt-d: Implement device and iommu preserve/unpreserve ops Samiullah Khawaja
2026-10-28 1:51 ` Baolu Lu
2026-10-28 3:10 ` Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 07/18] iommu/vt-d: Clear unpreserved context entries during shutdown Samiullah Khawaja
2026-10-28 3:18 ` Baolu Lu
2026-10-29 0:34 ` Samiullah Khawaja
2026-10-29 3:18 ` Baolu Lu
2026-10-29 22:00 ` Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 08/18] iommu: Add APIs to get iommu and device preserved state Samiullah Khawaja
2026-10-30 6:03 ` Baolu Lu
2026-10-31 1:55 ` Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 09/18] iommu/vt-d: Combine disable_dmar_iommu() and free_dmar_iommu() Samiullah Khawaja
2026-10-28 6:01 ` Baolu Lu
2026-10-29 0:33 ` Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 10/18] iommu/vt-d: Restore IOMMU state and reclaimed domain ids Samiullah Khawaja
2026-10-28 7:14 ` Baolu Lu
2026-10-29 0:32 ` Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 11/18] iommu/vt-d: Preserve PASID table of preserved device Samiullah Khawaja
2026-10-29 7:42 ` Baolu Lu
2026-10-25 2:19 ` [PATCH v6 12/18] iommu: Restore and reattach preserved domains to devices Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 13/18] iommu/vt-d: Handle reattach of the restored domain Samiullah Khawaja
2026-10-29 8:28 ` Baolu Lu
2026-10-29 22:34 ` Samiullah Khawaja
2026-10-29 23:38 ` Baolu Lu
2026-10-30 19:39 ` Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 14/18] iommufd: Implement ioctl to mark HWPT for preservation Samiullah Khawaja
2026-10-30 7:20 ` Baolu Lu
2026-10-31 1:48 ` Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 15/18] iommufd: Persist iommu hardware pagetables for live update Samiullah Khawaja
2026-10-31 2:46 ` Baolu Lu
2026-10-31 3:24 ` Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 16/18] iommufd: Add APIs to preserve/unpreserve a vfio cdev Samiullah Khawaja
2026-10-31 3:31 ` Baolu Lu
2026-10-31 3:57 ` Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 17/18] vfio/pci: Preserve the iommufd state of the " Samiullah Khawaja
2026-10-31 5:56 ` Baolu Lu
2026-10-25 2:19 ` [PATCH v6 18/18] iommufd/selftest: Add test to verify iommufd preservation Samiullah Khawaja
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=38384919-f0e5-4c93-b71b-065b96a74c38@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=Ankit.Soni@amd.com \
--cc=akpm@linux-foundation.org \
--cc=alex@shazbot.org \
--cc=dev@jstarks.net \
--cc=dmatlack@google.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--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=pasha.tatashin@soleen.com \
--cc=praan@google.com \
--cc=pratyush@kernel.org \
--cc=robin.murphy@arm.com \
--cc=shuah@kernel.org \
--cc=skhawaja@google.com \
--cc=vipinsh@google.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
all inboxes | Powered by JetHome®