Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Samiullah Khawaja <skhawaja@google.com>,
	Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	David Woodhouse <dwmw2@infradead.org>
Cc: baolu.lu@linux.intel.com, Pranjal Shrivastava <praan@google.com>,
	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>,
	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 17/18] vfio/pci: Preserve the iommufd state of the vfio cdev
Date: Sat, 31 Oct 2026 13:56:12 +0800	[thread overview]
Message-ID: <2574cbc8-8c2b-4458-9fcd-b077190084a3@linux.intel.com> (raw)
In-Reply-To: <20261025021930.674647-18-skhawaja@google.com>

On 10/25/2026 10:19 AM, Samiullah Khawaja wrote:
> If the vfio cdev is attached to an iommufd, preserve the state of the
> attached iommufd also. Basically preserve the iommu specific state of
> the device and also the attach iommu HW unit.
> 
> Once the device and its iommufd attachment is preserved, it cannot be
> detached or attached to another IOAS until it is unpreserved.
> 
> Reviewed-by: Pranjal Shrivastava <praan@google.com>
> Signed-off-by: Samiullah Khawaja <skhawaja@google.com>
> ---
>   drivers/vfio/device_cdev.c             | 10 +++++++++
>   drivers/vfio/pci/vfio_pci_liveupdate.c | 28 ++++++++++++++++++++++++--
>   2 files changed, 36 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/vfio/device_cdev.c b/drivers/vfio/device_cdev.c
> index b818aab92f76..4eb7ffd489bd 100644
> --- a/drivers/vfio/device_cdev.c
> +++ b/drivers/vfio/device_cdev.c
> @@ -284,6 +284,11 @@ int vfio_df_ioctl_attach_pt(struct vfio_device_file *df,
>   	}
>   
>   	mutex_lock(&device->dev_set->lock);
> +	if (iommufd_device_is_preserved(device->iommufd_device)) {
> +		ret = -EBUSY;
> +		goto out_unlock;
> +	}
> +
>   	if (attach.flags & VFIO_DEVICE_ATTACH_PASID)
>   		ret = device->ops->pasid_attach_ioas(device,
>   						     attach.pasid,
> @@ -342,6 +347,11 @@ int vfio_df_ioctl_detach_pt(struct vfio_device_file *df,
>   	}
>   
>   	mutex_lock(&device->dev_set->lock);
> +	if (iommufd_device_is_preserved(device->iommufd_device)) {
> +		mutex_unlock(&device->dev_set->lock);
> +		return -EBUSY;
> +	}
> +
>   	if (detach.flags & VFIO_DEVICE_DETACH_PASID)
>   		device->ops->pasid_detach_ioas(device, detach.pasid);
>   	else
> diff --git a/drivers/vfio/pci/vfio_pci_liveupdate.c b/drivers/vfio/pci/vfio_pci_liveupdate.c
> index f0ea37d98696..fb2141ee8942 100644
> --- a/drivers/vfio/pci/vfio_pci_liveupdate.c
> +++ b/drivers/vfio/pci/vfio_pci_liveupdate.c
> @@ -106,6 +106,7 @@
>   
>   #include <linux/errno.h>
>   #include <linux/file.h>
> +#include <linux/iommufd.h>
>   #include <linux/kexec_handover.h>
>   #include <linux/kho/abi/vfio_pci.h>
>   #include <linux/liveupdate.h>
> @@ -114,6 +115,8 @@
>   
>   #include "vfio_pci_priv.h"
>   
> +MODULE_IMPORT_NS("IOMMUFD");
> +
>   static bool vfio_pci_liveupdate_can_preserve(struct liveupdate_file_handler *handler,
>   					     struct file *file)
>   {
> @@ -154,15 +157,25 @@ static int vfio_pci_liveupdate_preserve(struct liveupdate_file_op_args *args)
>   	struct vfio_pci_core_device_ser *ser;
>   	struct vfio_pci_core_device *vdev;
>   	struct pci_dev *pdev;
> -	int ret;
> +	u64 iommufd_token;
> +	int ret = 0;

nit: no need to initialize ret.

>   
>   	vdev = container_of(device, struct vfio_pci_core_device, vdev);
>   	pdev = vdev->pdev;
>   
> -	ret = pci_liveupdate_preserve(pdev);
> +	mutex_lock(&device->dev_set->lock);
> +	ret = iommufd_device_preserve(args->session,
> +				      device->iommufd_device,
> +				      &iommufd_token);
> +	mutex_unlock(&device->dev_set->lock);
> +
>   	if (ret)
>   		return ret;
>   
> +	ret = pci_liveupdate_preserve(pdev);
> +	if (ret)
> +		goto err_iommufd_unpreserve;
> +
>   	ser = kho_alloc_preserve(sizeof(*ser));
>   	if (IS_ERR(ser)) {
>   		ret = PTR_ERR(ser);
> @@ -177,6 +190,12 @@ static int vfio_pci_liveupdate_preserve(struct liveupdate_file_op_args *args)
>   
>   err_unpreserve:
>   	pci_liveupdate_unpreserve(pdev);
> +
> +err_iommufd_unpreserve:
> +	mutex_lock(&device->dev_set->lock);
> +	iommufd_device_unpreserve(args->session,
> +				  device->iommufd_device);
> +	mutex_unlock(&device->dev_set->lock);
>   	return ret;
>   }
>   
> @@ -184,6 +203,11 @@ static void vfio_pci_liveupdate_unpreserve(struct liveupdate_file_op_args *args)
>   {
>   	struct vfio_device *device = vfio_device_from_file(args->file);
>   
> +	mutex_lock(&device->dev_set->lock);
> +	iommufd_device_unpreserve(args->session,
> +				  device->iommufd_device);
> +	mutex_unlock(&device->dev_set->lock);
> +
>   	pci_liveupdate_unpreserve(to_pci_dev(device->dev));
>   	kho_unpreserve_free(phys_to_virt(args->serialized_data));
>   }

Unpreservation isn't the exact reverse of preservation. Anything special
here?

Otherwise, this patch looks good to me,

Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>

  reply	other threads:[~2026-10-31  5:56 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
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 [this message]
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=2574cbc8-8c2b-4458-9fcd-b077190084a3@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