mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Samiullah Khawaja <skhawaja@google.com>,
	David Woodhouse <dwmw2@infradead.org>,
	Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
	Pasha Tatashin <pasha.tatashin@soleen.com>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	iommu@lists.linux.dev
Cc: Robin Murphy <robin.murphy@arm.com>,
	Pratyush Yadav <pratyush@kernel.org>,
	Kevin Tian <kevin.tian@intel.com>,
	Alex Williamson <alex@shazbot.org>,
	linux-kernel@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>,
	Vipin Sharma <vipinsh@google.com>,
	dmatlack@google.com, YiFei Zhu <zhuyifei@google.com>,
	Chris Li <chrisl@kernel.org>,
	praan@google.com
Subject: Re: [RFC PATCH v2 21/32] iommu/vt-d: Clean the context entries of unpreserved devices
Date: Thu, 4 Dec 2025 14:28:25 +0800	[thread overview]
Message-ID: <52bed033-fa16-4429-a1c6-d8f24961b5ef@linux.intel.com> (raw)
In-Reply-To: <20251202230303.1017519-22-skhawaja@google.com>

On 12/3/25 07:02, Samiullah Khawaja wrote:
> During normal shutdown the iommu translation is disabled. Since the root
> table is preserved during live update, it needs to be cleaned up and the
> context entries of the unpreserved devices need to be cleared.
> 
> Signed-off-by: Samiullah Khawaja<skhawaja@google.com>
> ---
>   drivers/iommu/intel/iommu.c      | 33 ++++++++++++++++++++++++++++++--
>   drivers/iommu/intel/iommu.h      |  1 +
>   drivers/iommu/intel/liveupdate.c |  1 +
>   3 files changed, 33 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
> index 3f69a073b2d8..84fef81ecf4d 100644
> --- a/drivers/iommu/intel/iommu.c
> +++ b/drivers/iommu/intel/iommu.c
> @@ -16,6 +16,7 @@
>   #include <linux/crash_dump.h>
>   #include <linux/dma-direct.h>
>   #include <linux/dmi.h>
> +#include <linux/iommu-lu.h>
>   #include <linux/memory.h>
>   #include <linux/pci.h>
>   #include <linux/pci-ats.h>
> @@ -52,6 +53,10 @@ static int rwbf_quirk;
>   
>   #define rwbf_required(iommu)	(rwbf_quirk || cap_rwbf((iommu)->cap))
>   
> +#ifdef CONFIG_LIVEUPDATE
> +static void __clean_unpreserved_context_entries(struct intel_iommu *iommu);
> +#endif
> +
>   /*
>    * set to 1 to panic kernel if can't successfully enable VT-d
>    * (used when kernel is launched w/ TXT)
> @@ -2376,8 +2381,12 @@ void intel_iommu_shutdown(void)
>   		/* Disable PMRs explicitly here. */
>   		iommu_disable_protect_mem_regions(iommu);
>   
> -		/* Make sure the IOMMUs are switched off */
> -		iommu_disable_translation(iommu);
> +		if (iommu->iommu.outgoing_preserved_state) {
> +			__clean_unpreserved_context_entries(iommu);
> +		} else {
> +			/* Make sure the IOMMUs are switched off */
> +			iommu_disable_translation(iommu);
> +		}
>   	}
>   }
>   
> @@ -2884,6 +2893,26 @@ static const struct iommu_dirty_ops intel_second_stage_dirty_ops = {
>   	.set_dirty_tracking = intel_iommu_set_dirty_tracking,
>   };
>   
> +static void __clean_unpreserved_context_entries(struct intel_iommu *iommu)
> +{
> +	struct device_domain_info *info;
> +	struct pci_dev *pdev = NULL;
> +
> +	for_each_pci_dev(pdev) {
> +		info = dev_iommu_priv_get(&pdev->dev);
> +		if (!info)
> +			continue;

I assume the per-device iommu private data is freed in the
release_device path, which runs before intel_iommu_shutdown(). If that
is the case, "info" would always be NULL here, resulting the subsequent
code dead code. Or not?

> +
> +		if (info->iommu != iommu)
> +			continue;
> +
> +		if (dev_iommu_preserved_state(&pdev->dev))
> +			continue;
> +
> +		domain_context_clear(info);
> +	}
> +}

Thanks,
baolu

  reply	other threads:[~2025-12-04  6:32 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02 23:02 [RFC PATCH v2 00/32] Add live update state preservation Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 01/32] iommufd: Allow HWPTs to have a NULL IOAS Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 02/32] iommufd: split alloc and domain assign from iommufd_hwpt_paging_alloc Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 03/32] iommufd: Add basic skeleton based on liveupdate_file_handler Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 04/32] iommufd-lu: Implement basic prepare/cancel/finish/retrieve using folios Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 05/32] iommufd-lu: Implement ioctl to let userspace mark an HWPT to be preserved Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 06/32] iommufd-lu: Persist iommu hardware pagetables for live update Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 07/32] iommu: Add liveupdate FLB for IOMMU state preservation Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 08/32] iommu: Register IOMMU FLB with iommufd file handler Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 09/32] iommu: Implement IOMMU LU FLB preserve/unpreserve callbacks Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 10/32] iommu: Add iommu_domain ops to preserve, unpreserve and restore Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 11/32] iommu/pages: Add APIs to preserve/unpreserve/restore iommu pages Samiullah Khawaja
2025-12-04  2:25   ` Baolu Lu
2025-12-04 17:39     ` Samiullah Khawaja
2025-12-05  4:58       ` Baolu Lu
2025-12-02 23:02 ` [RFC PATCH v2 12/32] iommupt: Implement preserve/unpreserve/restore callbacks Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 13/32] iommu: Add APIs to preserve/unpreserve iommu domains Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 14/32] iommufd: Use the iommu_domain_preserve/unpreserve APIs Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 15/32] iommu: Add API to keep track of iommu domain attachments Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 16/32] iommu: Add API to preserve/unpreserve a device Samiullah Khawaja
2025-12-04  5:46   ` Baolu Lu
2025-12-04 17:47     ` Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 17/32] iommu/vt-d: Implement device and iommu preserve/unpreserve ops Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 18/32] iommufd: Add APIs to preserve/unpreserve a vfio cdev Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 19/32] vfio/pci: Preserve the iommufd state of the " Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 20/32] iommu: Add APIs to get preserved state of a device Samiullah Khawaja
2025-12-04  6:19   ` Baolu Lu
2025-12-04 17:48     ` Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 21/32] iommu/vt-d: Clean the context entries of unpreserved devices Samiullah Khawaja
2025-12-04  6:28   ` Baolu Lu [this message]
2025-12-02 23:02 ` [RFC PATCH v2 22/32] iommu: Implement IOMMU FLB retrieve and finish ops Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 23/32] iommu: Add an API get the preserved state of an IOMMU Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 24/32] iommu/vt-d: restore state of the preserved IOMMU Samiullah Khawaja
2025-12-04  6:43   ` Baolu Lu
2025-12-04 17:55     ` Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 25/32] iommu: Add helper APIs to fetch preserved device state Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 26/32] iommu/vt-d: reclaim domain ids of the preserved devices Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 27/32] iommu: restore preserved domain and reattach Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 28/32] iommu/vt-d: reuse the preserved domain id for preserved devices Samiullah Khawaja
2025-12-02 23:02 ` [RFC PATCH v2 29/32] iommufd: Handle the iommufd can_finish properly Samiullah Khawaja
2025-12-02 23:03 ` [RFC PATCH v2 30/32] iommu: Transfer device ownership after liveupdate Samiullah Khawaja
2025-12-02 23:03 ` [RFC PATCH v2 31/32] iommu: Allow replacing restored domain Samiullah Khawaja
2025-12-02 23:03 ` [RFC PATCH v2 32/32] iommufd/selftest: Add test to verify iommufd preservation Samiullah Khawaja
2026-01-28 19:59 ` [RFC PATCH v2 00/32] Add live update state preservation Jason Gunthorpe
2026-01-29  1:11   ` Samiullah Khawaja
2026-02-02 22:45     ` David Matlack
2026-02-02 23:00       ` Samiullah Khawaja
2026-02-02 23:46         ` Jason Gunthorpe
2026-02-02 23:45       ` 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=52bed033-fa16-4429-a1c6-d8f24961b5ef@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=ajayachandra@nvidia.com \
    --cc=alex@shazbot.org \
    --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=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=skhawaja@google.com \
    --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

Powered by JetHome