From: Mostafa Saleh <smostafa@google.com>
To: linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, will@kernel.org,
robin.murphy@arm.com, joro@8bytes.org
Cc: jgg@ziepe.ca, nicolinc@nvidia.com, mshavit@google.com,
Mostafa Saleh <smostafa@google.com>
Subject: [PATCH 2/2] iommu/arm-smmu-v3: Report stalled S2 events
Date: Mon, 12 Aug 2024 20:52:55 +0000 [thread overview]
Message-ID: <20240812205255.97781-3-smostafa@google.com> (raw)
In-Reply-To: <20240812205255.97781-1-smostafa@google.com>
Previously, S2 stall was disabled and in case there was an event it
wouldn't be reported on the assumption that it's always pinned by VFIO.
However, now since we can enable stall, devices that use S2 outside
VFIO should be able to report the stalls similar to S1.
Also, to keep the old behaviour were S2 events from nested domains were
not reported as they are pinned (from VFIO) add a new flag to track this.
Signed-off-by: Mostafa Saleh <smostafa@google.com>
---
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 18 +++++++++++++-----
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h | 2 ++
2 files changed, 15 insertions(+), 5 deletions(-)
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 8d573d9ca93c..ffa865529d73 100644
--- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
+++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
@@ -1733,6 +1733,7 @@ static int arm_smmu_handle_evt(struct arm_smmu_device *smmu, u64 *evt)
u32 sid = FIELD_GET(EVTQ_0_SID, evt[0]);
struct iopf_fault fault_evt = { };
struct iommu_fault *flt = &fault_evt.fault;
+ struct arm_smmu_domain *smmu_domain;
switch (FIELD_GET(EVTQ_0_ID, evt[0])) {
case EVT_ID_TRANSLATION_FAULT:
@@ -1744,10 +1745,6 @@ static int arm_smmu_handle_evt(struct arm_smmu_device *smmu, u64 *evt)
return -EOPNOTSUPP;
}
- /* Stage-2 is always pinned at the moment */
- if (evt[1] & EVTQ_1_S2)
- return -EFAULT;
-
if (!(evt[1] & EVTQ_1_STALL))
return -EOPNOTSUPP;
@@ -1782,6 +1779,15 @@ static int arm_smmu_handle_evt(struct arm_smmu_device *smmu, u64 *evt)
goto out_unlock;
}
+ /* It is guaranteed that smmu_domain exists as EVTQ_1_STALL is checked. */
+ smmu_domain = to_smmu_domain(iommu_get_domain_for_dev(master->dev));
+
+ /* nesting domain is always pinned at the moment */
+ if (smmu_domain->enable_nesting) {
+ ret = -EINVAL;
+ goto out_unlock;
+ }
+
iommu_report_device_fault(master->dev, &fault_evt);
out_unlock:
mutex_unlock(&smmu->streams_mutex);
@@ -3373,8 +3379,10 @@ static int arm_smmu_enable_nesting(struct iommu_domain *domain)
mutex_lock(&smmu_domain->init_mutex);
if (smmu_domain->smmu)
ret = -EPERM;
- else
+ else {
smmu_domain->stage = ARM_SMMU_DOMAIN_S2;
+ smmu_domain->enable_nesting = true;
+ }
mutex_unlock(&smmu_domain->init_mutex);
return ret;
diff --git a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h
index 0dc7ad43c64c..f66efeec2cf8 100644
--- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h
+++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h
@@ -745,6 +745,8 @@ struct arm_smmu_domain {
spinlock_t devices_lock;
struct mmu_notifier mmu_notifier;
+
+ bool enable_nesting;
};
/* The following are exposed for testing purposes. */
--
2.46.0.76.ge559c4bf1a-goog
next prev parent reply other threads:[~2024-08-12 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 20:52 [PATCH 0/2] Fix handling of S2 stalls Mostafa Saleh
2024-08-12 20:52 ` [PATCH 1/2] iommu/arm-smmu-v3: Match Stall behaviour for S2 Mostafa Saleh
2024-08-13 11:46 ` Robin Murphy
2024-08-13 13:40 ` Mostafa Saleh
2024-08-13 17:01 ` Jason Gunthorpe
2024-08-12 20:52 ` Mostafa Saleh [this message]
2024-08-13 11:57 ` [PATCH 2/2] iommu/arm-smmu-v3: Report stalled S2 events Robin Murphy
2024-08-13 13:43 ` Mostafa Saleh
2024-08-13 17:51 ` Jason Gunthorpe
2024-08-14 9:58 ` Mostafa Saleh
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=20240812205255.97781-3-smostafa@google.com \
--to=smostafa@google.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mshavit@google.com \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.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;
as well as URLs for NNTP newsgroup(s).