From: Nicolin Chen <nicolinc@nvidia.com>
To: <will@kernel.org>
Cc: <robin.murphy@arm.com>, <joro@8bytes.org>, <jgg@nvidia.com>,
<praan@google.com>, <mmarrid@nvidia.com>, <kees@kernel.org>,
<Alexander.Grest@microsoft.com>, <baolu.lu@linux.intel.com>,
<smostafa@google.com>, <linux-arm-kernel@lists.infradead.org>,
<iommu@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<bbiber@nvidia.com>, <skaestle@nvidia.com>
Subject: [PATCH rc] iommu/arm-smmu-v3: Drain in-flight fault handlers
Date: Fri, 6 Mar 2026 16:17:23 -0800 [thread overview]
Message-ID: <20260307001723.964956-1-nicolinc@nvidia.com> (raw)
From: Malak Marrid <mmarrid@nvidia.com>
When a device is switching away from a domain, either through a detach or a
replace operation, it must drain its IOPF queue that only contains the page
requests for the old domain.
Currently, the IOPF infrastructure is used by master->stall_enabled. So the
stalled transaction for the old domain should be resumed/terminated. Fix it
properly.
Fixes: cfea71aea921 ("iommu/arm-smmu-v3: Put iopf enablement in the domain attach path")
Cc: stable@vger.kernel.org
Co-developed-by: Barak Biber <bbiber@nvidia.com>
Signed-off-by: Barak Biber <bbiber@nvidia.com>
Co-developed-by: Stefan Kaestle <skaestle@nvidia.com>
Signed-off-by: Stefan Kaestle <skaestle@nvidia.com>
Signed-off-by: Malak Marrid <mmarrid@nvidia.com>
Signed-off-by: Nicolin Chen <nicolinc@nvidia.com>
---
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
index 4d00d796f0783..2176ee8bec767 100644
--- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
+++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
@@ -2843,6 +2843,12 @@ static int arm_smmu_enable_iopf(struct arm_smmu_master *master,
if (master->iopf_refcount) {
master->iopf_refcount++;
master_domain->using_iopf = true;
+ /*
+ * If the device is already on the IOPF queue (domain replace),
+ * drain in-flight fault handlers so nothing will hold the old
+ * domain when the core switches the attach handle.
+ */
+ iopf_queue_flush_dev(master->dev);
return 0;
}
@@ -2866,8 +2872,11 @@ static void arm_smmu_disable_iopf(struct arm_smmu_master *master,
return;
master->iopf_refcount--;
- if (master->iopf_refcount == 0)
+ if (master->iopf_refcount == 0) {
+ /* Drain in-flight fault handlers before removing device */
+ iopf_queue_flush_dev(master->dev);
iopf_queue_remove_device(master->smmu->evtq.iopf, master->dev);
+ }
}
static void arm_smmu_remove_master_domain(struct arm_smmu_master *master,
--
2.43.0
next reply other threads:[~2026-03-07 0:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 0:17 Nicolin Chen [this message]
2026-03-12 13:51 ` [PATCH rc] iommu/arm-smmu-v3: Drain in-flight fault handlers Will Deacon
2026-03-12 14:25 ` Jason Gunthorpe
2026-03-24 14:04 ` Will Deacon
2026-03-24 14:17 ` Jason Gunthorpe
2026-03-24 14:35 ` Will Deacon
2026-03-24 18:53 ` 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=20260307001723.964956-1-nicolinc@nvidia.com \
--to=nicolinc@nvidia.com \
--cc=Alexander.Grest@microsoft.com \
--cc=baolu.lu@linux.intel.com \
--cc=bbiber@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kees@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarrid@nvidia.com \
--cc=praan@google.com \
--cc=robin.murphy@arm.com \
--cc=skaestle@nvidia.com \
--cc=smostafa@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