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: 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 07/18] iommu/vt-d: Clear unpreserved context entries during shutdown
Date: Wed, 28 Oct 2026 11:18:40 +0800 [thread overview]
Message-ID: <3a31d343-68e2-4329-bd72-76a80b4edf81@linux.intel.com> (raw)
In-Reply-To: <20261025021930.674647-8-skhawaja@google.com>
On 10/25/26 10:19, 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 and root entries for the
> unpreserved context tables need to be cleared.
>
> This is required because during kexec reboot and shutdown the devices do
> not go through the release flow, so there might be stale entries in the
> root table and context tables. Also note that new unpreserved context
> tables for unpreserved devices might have been added after preservation,
> so the root table entries for unpreserved context tables also need to
> removed.
>
> Signed-off-by: Samiullah Khawaja <skhawaja@google.com>
> ---
> drivers/iommu/intel/iommu.c | 15 +++-
> drivers/iommu/intel/iommu.h | 5 ++
> drivers/iommu/intel/liveupdate.c | 134 +++++++++++++++++++++++++++++++
> 3 files changed, 152 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
> index 14bd1ca4fbd5..23a1da351ddf 100644
> --- a/drivers/iommu/intel/iommu.c
> +++ b/drivers/iommu/intel/iommu.c
> @@ -1967,6 +1967,14 @@ static int iommu_suspend(void *data)
>
> iommu_flush_all();
>
> + /*
> + * Note that IOMMU suspend doesn't affect live update. The state
> + * preserved during live update is not released and remains valid during
> + * suspend and reused during IOMMU resume.
> + *
> + * Also note deployment of suspend/resume and live updated use case
> + * should be mostly mutually exclusive.
> + */
> for_each_active_iommu(iommu, drhd) {
> iommu_disable_translation(iommu);
>
> @@ -2512,8 +2520,11 @@ 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);
> + /* Make sure the IOMMUs are switched off if not preserved. */
> + if (iommu_preserved_state(&iommu->iommu))
> + clear_unpreserved_context_entries(iommu);
> + else
> + iommu_disable_translation(iommu);
> }
> }
>
> diff --git a/drivers/iommu/intel/iommu.h b/drivers/iommu/intel/iommu.h
> index a6c0ed55db30..16ab103d308a 100644
> --- a/drivers/iommu/intel/iommu.h
> +++ b/drivers/iommu/intel/iommu.h
> @@ -1316,6 +1316,11 @@ int intel_iommu_preserve(struct iommu_device *iommu,
> struct iommu_hw_ser *iommu_ser);
> void intel_iommu_unpreserve(struct iommu_device *iommu,
> struct iommu_hw_ser *iommu_ser);
> +void clear_unpreserved_context_entries(struct intel_iommu *iommu);
> +#else
> +static inline void clear_unpreserved_context_entries(struct intel_iommu *iommu)
> +{
> +}
> #endif
>
> #ifdef CONFIG_INTEL_IOMMU_SVM
> diff --git a/drivers/iommu/intel/liveupdate.c b/drivers/iommu/intel/liveupdate.c
> index 0047f9d92cbc..f92cb774cc99 100644
> --- a/drivers/iommu/intel/liveupdate.c
> +++ b/drivers/iommu/intel/liveupdate.c
> @@ -82,6 +82,140 @@ static int preserve_context_table(struct intel_iommu *iommu,
> return 0;
> }
>
> +static void clear_unpreserved_context_root_entries(struct intel_iommu *iommu,
> + struct iommu_hw_ser *ser)
> +{
> + struct root_entry *root;
> + int i;
> +
> + /*
> + * Individual invalidations for each context table removal are not
> + * needed as we issue global invalidations later.
> + */
> + for (i = 0; i < ROOT_ENTRY_NR; i++) {
> + root = &iommu->root_entry[i];
> +
> + if (!is_context_table_preserved(iommu, ser, i, 0) && (root->lo & 1)) {
> + root->lo = 0;
> + __iommu_flush_cache(iommu,
> + &root->lo,
> + sizeof(root->lo));
> + }
> +
> + if (!sm_supported(iommu))
> + continue;
> +
> + if (!is_context_table_preserved(iommu, ser, i, 0x80) && (root->hi & 1)) {
> + root->hi = 0;
> + __iommu_flush_cache(iommu,
> + &root->hi,
> + sizeof(root->hi));
> + }
> + }
> +}
> +
> +static void clear_unpreserved_context(struct device_domain_info *info, u8 bus, u8 devfn)
> +{
> + struct context_entry *context;
> +
> + /*
> + * This cleanup is done during shutdown, so it should be fine to only
> + * clear the entries here and issue one global invalidation later to
> + * invalidate all cleared entries.
> + *
> + * Note that the device IOTLB invalidation for unpreserved devices is
> + * skipped this way. This matches the normal kexec reboot, where the
> + * IOMMU translation is disabled without invalidating the device IOTLBs,
> + * and the unpreserved devices go through the same flow in the next
> + * kernel as they do after a normal kexec reboot. Issuing device IOTLB
> + * invalidations this late during shutdown could also cause invalidation
> + * timeouts, as drivers might have moved devices to a low power state,
> + * and would add to the shutdown time.
> + *
> + * The iommu lock is not needed as the context tables are never removed
> + * and the new ones are not added during shutdown.
> + */
> + context = iommu_context_addr(info->iommu, bus, devfn, 0);
> + if (context) {
> + /*
> + * Individual invalidations are not needed as we issue global
> + * invalidations later once all the cleanups are done.
> + */
> + context_clear_present(context);
> + __iommu_flush_cache(info->iommu, context, sizeof(*context));
> + context_clear_entry(context);
> + __iommu_flush_cache(info->iommu, context, sizeof(*context));
> + }
> +}
> +
> +static int clear_unpreserved_alias_cb(struct pci_dev *pdev, u16 alias, void *data)
> +{
> + struct device_domain_info *info = data;
> +
> + clear_unpreserved_context(info, PCI_BUS_NUM(alias), alias & 0xff);
> + return 0;
> +}
> +
> +static int clear_unpreserve_context_entry_fn(struct device *dev,
> + struct iommu_device *iommu_dev)
> +{
> + struct device_domain_info *info;
> +
> + info = dev_iommu_priv_get(dev);
> + if (!info)
> + return 0;
> +
> + if (dev_iommu_preserved_state(dev))
> + return 0;
> +
> + if (dev_is_pci(dev))
> + pci_for_each_dma_alias(to_pci_dev(dev),
> + clear_unpreserved_alias_cb, info);
> + else
> + clear_unpreserved_context(info, info->bus, info->devfn);
> +
> + return 0;
> +}
> +
> +/**
> + * clear_unpreserved_context_entries() - Clear context entries for unpreserved devices
> + * @iommu: Target IOMMU
> + *
> + * Clear the context entries of unpreserved devices during shutdown before kexec.
> + */
> +void clear_unpreserved_context_entries(struct intel_iommu *iommu)
> +{
> + /*
> + * Clear context entries for unpreserved devices because during kexec
> + * reboot and shutdown the devices do not go through the release flow,
> + * so there might be stale entries in the root table and context tables.
> + *
> + * Note that the error can be ignored as the iterator function does not
> + * fail.
> + */
> + iommu_for_each_dev(&iommu->iommu, clear_unpreserve_context_entry_fn);
> +
> + /*
> + * New unpreserved context tables for unpreserved devices might have
> + * been added after preservation, so the root table entries for
> + * unpreserved context tables need to be removed.
> + */
> + clear_unpreserved_context_root_entries(iommu,
> + iommu_preserved_state(&iommu->iommu));
> +
> + /*
> + * Some devices might not have teardown/detached properly depending on
> + * whether a proper device remove is done before kexec is triggered.
> + * Also unpreserved context tables and entries are removed during
> + * shutdown. So issue global invalidations to remove references to
> + * unpreserved tables and entries.
> + */
> + iommu->flush.flush_context(iommu, 0, 0, 0, DMA_CCMD_GLOBAL_INVL);
> + if (sm_supported(iommu))
> + qi_flush_pasid_cache(iommu, 0, QI_PC_GLOBAL, 0);
> + iommu->flush.flush_iotlb(iommu, 0, 0, 0, DMA_TLB_GLOBAL_FLUSH);
> +}
> +
> static void unpreserve_iommu_context_tables(struct intel_iommu *iommu,
> struct iommu_hw_ser *ser)
> {
This patch looks good to me,
Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>
next prev parent reply other threads:[~2026-10-28 3:18 UTC|newest]
Thread overview: 24+ 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-25 2:19 ` [PATCH v6 03/18] iommupt: Implement preserve/unpreserve/restore callbacks Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 04/18] iommu: Implement IOMMU domain preservation Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 05/18] iommu: Implement device and IOMMU HW preservation Samiullah Khawaja
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 [this message]
2026-10-25 2:19 ` [PATCH v6 08/18] iommu: Add APIs to get iommu and device preserved state 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-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-25 2:19 ` [PATCH v6 11/18] iommu/vt-d: Preserve PASID table of preserved device Samiullah Khawaja
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-25 2:19 ` [PATCH v6 14/18] iommufd: Implement ioctl to mark HWPT for preservation Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 15/18] iommufd: Persist iommu hardware pagetables for live update Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 16/18] iommufd: Add APIs to preserve/unpreserve a vfio cdev Samiullah Khawaja
2026-10-25 2:19 ` [PATCH v6 17/18] vfio/pci: Preserve the iommufd state of the " Samiullah Khawaja
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=3a31d343-68e2-4329-bd72-76a80b4edf81@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®