The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Samiullah Khawaja <skhawaja@google.com>
To: Pranjal Shrivastava <praan@google.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	 Lu Baolu <baolu.lu@linux.intel.com>,
	Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
	 Jason Gunthorpe <jgg@ziepe.ca>,
	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, Saeed Mahameed <saeedm@nvidia.com>,
	 Adithya Jayachandran <ajayachandra@nvidia.com>,
	Parav Pandit <parav@nvidia.com>,
	 Leon Romanovsky <leonro@nvidia.com>,
	William Tu <witu@nvidia.com>,
	 Pratyush Yadav <pratyush@kernel.org>,
	Pasha Tatashin <pasha.tatashin@soleen.com>,
	 David Matlack <dmatlack@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	 Chris Li <chrisl@kernel.org>, Vipin Sharma <vipinsh@google.com>,
	 YiFei Zhu <zhuyifei@google.com>
Subject: Re: [PATCH v2 04/16] iommu: Implement device and IOMMU HW preservation
Date: Mon, 18 May 2026 18:44:30 +0000	[thread overview]
Message-ID: <agtcSw4s0M2ArWI4@google.com> (raw)
In-Reply-To: <agsaY9714WS1N4Zu@google.com>

On Mon, May 18, 2026 at 01:55:47PM +0000, Pranjal Shrivastava wrote:
>On Mon, Apr 27, 2026 at 05:56:21PM +0000, Samiullah Khawaja wrote:
>> Add IOMMU ops to preserve/unpreserve a device. These 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/liveupdate.c       | 162 +++++++++++++++++++++++++++++++
>>  include/linux/iommu-liveupdate.h |  33 +++++++
>>  include/linux/iommu.h            |  20 ++++
>>  3 files changed, 215 insertions(+)
>>
>> diff --git a/drivers/iommu/liveupdate.c b/drivers/iommu/liveupdate.c
>> index f71f14518248..765d042e22e3 100644
>> --- a/drivers/iommu/liveupdate.c
>> +++ b/drivers/iommu/liveupdate.c
>> @@ -11,6 +11,7 @@
>>  #include <linux/liveupdate.h>
>>  #include <linux/iommu-liveupdate.h>
>>  #include <linux/iommu.h>
>> +#include <linux/pci.h>
>>  #include <linux/errno.h>
>>
>>  #define iommu_max_objs_per_page(_array) \
>> @@ -293,3 +294,164 @@ void iommu_domain_unpreserve(struct iommu_domain *domain)
>>  	domain->preserved_state = NULL;
>>  }
>>  EXPORT_SYMBOL_GPL(iommu_domain_unpreserve);
>> +
>> +static struct iommu_hw_ser *alloc_iommu_hw_ser(struct iommu_flb_obj *flb)
>> +{
>> +	int idx;
>> +
>> +	idx = alloc_object_ser((struct iommu_array_hdr_ser **)&flb->curr_iommu_array,
>> +			       iommu_max_objs_per_page(flb->curr_iommu_array));
>
>Nit: Same thing about brittle casts here, shall we make them void ** and
>cast then within alloc_object_set ?

Agreed. Will change this.
>
>
>> +	if (idx < 0)
>> +		return ERR_PTR(idx);
>> +
>> +	flb->curr_iommu_array->objects[idx].hdr.ref_count = 1;
>> +	return &flb->curr_iommu_array->objects[idx];
>> +}
>> +
>> +static int iommu_preserve_locked(struct iommu_device *iommu,
>> +				 struct iommu_flb_obj *flb_obj)
>> +{
>> +	struct iommu_hw_ser *iommu_hw_ser;
>> +	int ret;
>> +
>> +	if (!iommu->ops->preserve)
>> +		return -EOPNOTSUPP;
>> +
>> +	lockdep_assert_held(&flb_obj->lock);
>> +	if (iommu->outgoing_preserved_state) {
>> +		iommu->outgoing_preserved_state->hdr.ref_count++;
>> +		return 0;
>> +	}
>> +
>> +	iommu_hw_ser = alloc_iommu_hw_ser(flb_obj);
>> +	if (IS_ERR(iommu_hw_ser))
>> +		return PTR_ERR(iommu_hw_ser);
>> +
>> +	ret = iommu->ops->preserve(iommu, iommu_hw_ser);
>> +	if (ret) {
>> +		iommu_hw_ser->hdr.deleted = true;
>> +		return ret;
>> +	}
>> +
>> +	iommu->outgoing_preserved_state = iommu_hw_ser;
>> +	return ret;
>> +}
>> +
>> +static void iommu_unpreserve_locked(struct iommu_device *iommu,
>> +				    struct iommu_flb_obj *flb_obj)
>> +{
>> +	struct iommu_hw_ser *iommu_hw_ser = iommu->outgoing_preserved_state;
>> +
>> +	lockdep_assert_held(&flb_obj->lock);
>> +	iommu_hw_ser->hdr.ref_count--;
>> +	if (iommu_hw_ser->hdr.ref_count)
>
>Shall we add a defensive if (WARN_ON(!iommu_hw_ser)) ? I'm aware we
>check this on within iommu_unpreserve_device() but we don't seem to
>check it before calling iommu_unpreserve_locked() in the error path of
>iommu_preserve_device.

Agreed. I will add this.
>
>> +		return;
>> +
>> +	iommu->outgoing_preserved_state = NULL;
>> +	iommu->ops->unpreserve(iommu, iommu_hw_ser);
>
>We seem to assume we'll always have unpreserve implemented? If so, we
>should check it during the iommu registration itself and fail it, i.e.
>
>inside iommu_device_register() we could add something like:
>
>#ifdef CONFIG_IOMMU_LIVEUPDATE
>if ((iommu->ops->preserve && !iommu->ops->unpreserve) ||
>    (!iommu->ops->preserve && iommu->ops->unpreserve)) {
>        pr_err("IOMMU: %s: Asymmetric live-update operations detected\n",
>               dev_name(iommu->dev));
>        return -EINVAL;
>}
>#endif
>
>This prevents a half-baked iommu driver from ever spinning up, completely
>eliminating the need to check for it inside the live-update session paths.

Replied to this in the other thread where you suggested this inline with
Baolu's comment.
>
>> +	iommu_hw_ser->hdr.deleted = true;
>> +}
>> +
>> +static struct iommu_device_ser *alloc_iommu_device_ser(struct iommu_flb_obj *flb)
>> +{
>> +	int idx;
>> +
>> +	idx = alloc_object_ser((struct iommu_array_hdr_ser **)&flb->curr_device_array,
>
>Nit: Same thing about brittle casts here, shall we make them void ** and
>cast then within alloc_object_set ?

Will update this in next revision.
>
>> +			       iommu_max_objs_per_page(flb->curr_device_array));
>> +	if (idx < 0)
>> +		return ERR_PTR(idx);
>> +
>> +	flb->curr_device_array->objects[idx].hdr.ref_count = 1;
>> +	return &flb->curr_device_array->objects[idx];
>> +}
>> +

[snip]
>> +
>> +	ret = iommu_preserve_locked(iommu->iommu_dev, flb_obj);
>> +	if (ret) {
>> +		device_ser->hdr.deleted = true;
>> +		return ret;
>> +	}
>> +
>> +	device_ser->domain_iommu_ser.domain_phys = __pa(domain->preserved_state);
>> +	device_ser->domain_iommu_ser.iommu_phys = __pa(iommu->iommu_dev->outgoing_preserved_state);
>
>Nit: Should these be updated to use virt_to_phys as well?

Will update these.
>
>> +	device_ser->devid = pci_dev_id(pdev);
>> +	device_ser->pci_domain_nr = pci_domain_nr(pdev->bus);
>> +
>> +	ret = iommu->iommu_dev->ops->preserve_device(dev, device_ser);
>> +	if (ret) {
>> +		device_ser->hdr.deleted = true;
>> +		iommu_unpreserve_locked(iommu->iommu_dev, flb_obj);
>> +		return ret;
>> +	}
>> +
>> +	dev->iommu->device_ser = device_ser;
>> +	*preserved_state = virt_to_phys(device_ser);
>> +	return 0;
>> +}
>> +
>
>[...]
>
>Thanks,
>Praan
>

Sami

  reply	other threads:[~2026-05-18 18:44 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 17:56 [PATCH v2 00/16] iommu: Add live update state preservation Samiullah Khawaja
2026-04-27 17:56 ` [PATCH v2 01/16] liveupdate: luo_file: Add internal APIs for file preservation Samiullah Khawaja
2026-05-18 11:40   ` Pranjal Shrivastava
2026-05-18 19:08     ` Samiullah Khawaja
2026-04-27 17:56 ` [PATCH v2 02/16] iommu: Implement IOMMU Live update FLB callbacks Samiullah Khawaja
2026-05-01 21:45   ` David Matlack
2026-05-18 11:52     ` Pranjal Shrivastava
2026-05-18 14:10       ` Pratyush Yadav
2026-05-18 15:08         ` Pranjal Shrivastava
2026-05-18 12:33     ` Pranjal Shrivastava
2026-05-18 17:20       ` Samiullah Khawaja
2026-05-18 17:32         ` Pranjal Shrivastava
2026-05-18 17:06     ` Samiullah Khawaja
2026-04-27 17:56 ` [PATCH v2 03/16] iommu: Implement IOMMU domain preservation Samiullah Khawaja
2026-05-01 22:08   ` David Matlack
2026-05-04 18:33     ` Samiullah Khawaja
2026-05-18 13:13   ` Pranjal Shrivastava
2026-05-18 18:55     ` Samiullah Khawaja
2026-05-18 21:36       ` Pranjal Shrivastava
2026-04-27 17:56 ` [PATCH v2 04/16] iommu: Implement device and IOMMU HW preservation Samiullah Khawaja
2026-05-01 22:42   ` David Matlack
2026-05-04 19:06     ` Samiullah Khawaja
2026-05-07  2:07   ` Baolu Lu
2026-05-07 18:47     ` Samiullah Khawaja
2026-05-18 14:01       ` Pranjal Shrivastava
2026-05-18 18:33         ` Samiullah Khawaja
2026-05-18 13:55   ` Pranjal Shrivastava
2026-05-18 18:44     ` Samiullah Khawaja [this message]
2026-04-27 17:56 ` [PATCH v2 05/16] iommu/pages: Add APIs to preserve/unpreserve/restore iommu pages Samiullah Khawaja
2026-05-18 14:23   ` Pranjal Shrivastava
2026-05-18 17:22     ` Samiullah Khawaja
2026-04-27 17:56 ` [PATCH v2 06/16] iommupt: Implement preserve/unpreserve/restore callbacks Samiullah Khawaja
2026-05-07  2:55   ` Baolu Lu
2026-05-07 18:40     ` Samiullah Khawaja
2026-05-19 13:15   ` Pranjal Shrivastava
2026-05-19 17:14     ` Samiullah Khawaja
2026-04-27 17:56 ` [PATCH v2 07/16] iommu/vt-d: Implement device and iommu preserve/unpreserve ops Samiullah Khawaja
2026-05-07  6:25   ` Baolu Lu
2026-05-08  2:36     ` Samiullah Khawaja
2026-05-18 20:32       ` Samiullah Khawaja
2026-05-19 14:40         ` Pranjal Shrivastava
2026-05-19 18:26           ` Samiullah Khawaja
2026-04-27 17:56 ` [PATCH v2 08/16] iommu: Add APIs to get iommu and device preserved state Samiullah Khawaja
2026-05-19 15:52   ` Pranjal Shrivastava
2026-04-27 17:56 ` [PATCH v2 09/16] iommu/vt-d: Restore IOMMU state and reclaimed domain ids Samiullah Khawaja
2026-05-07  9:05   ` Baolu Lu
2026-05-07 17:35     ` Samiullah Khawaja
2026-05-19 21:46   ` Pranjal Shrivastava
2026-04-27 17:56 ` [PATCH v2 10/16] iommu: Restore and reattach preserved domains to devices Samiullah Khawaja
2026-05-07 13:54   ` Baolu Lu
2026-05-07 16:52     ` Samiullah Khawaja
2026-04-27 17:56 ` [PATCH v2 11/16] iommu/vt-d: preserve PASID table of preserved device Samiullah Khawaja
2026-05-08  6:05   ` Baolu Lu
2026-05-11 18:45     ` Samiullah Khawaja
2026-05-12 11:32       ` Baolu Lu
2026-05-19 22:35   ` Pranjal Shrivastava
2026-04-27 17:56 ` [PATCH v2 12/16] iommufd: Implement ioctl to mark HWPT for preservation Samiullah Khawaja
2026-05-19 23:05   ` Pranjal Shrivastava
2026-04-27 17:56 ` [PATCH v2 13/16] iommufd: Persist iommu hardware pagetables for live update Samiullah Khawaja
2026-05-20  0:00   ` Pranjal Shrivastava
2026-04-27 17:56 ` [PATCH v2 14/16] iommufd: Add APIs to preserve/unpreserve a vfio cdev Samiullah Khawaja
2026-05-20  0:46   ` Pranjal Shrivastava
2026-04-27 17:56 ` [PATCH v2 15/16] vfio/pci: Preserve the iommufd state of the " Samiullah Khawaja
2026-05-20  0:57   ` Pranjal Shrivastava
2026-04-27 17:56 ` [PATCH v2 16/16] 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=agtcSw4s0M2ArWI4@google.com \
    --to=skhawaja@google.com \
    --cc=ajayachandra@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex@shazbot.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=chrisl@kernel.org \
    --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=leonro@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parav@nvidia.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=praan@google.com \
    --cc=pratyush@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=saeedm@nvidia.com \
    --cc=shuah@kernel.org \
    --cc=vipinsh@google.com \
    --cc=will@kernel.org \
    --cc=witu@nvidia.com \
    --cc=zhuyifei@google.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