From: Jason Gunthorpe <jgg@ziepe.ca>
To: Jacob Pan <jacob.pan@linux.microsoft.com>
Cc: Shyam Saini <shyamsaini@linux.microsoft.com>,
iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, virtualization@lists.linux.dev,
will@kernel.org, eric.auger@redhat.com, code@tyhicks.com,
eahariha@linux.microsoft.com, vijayb@linux.microsoft.com
Subject: Re: [PATCH v2 0/3] arm-smmu: select suitable IOVA
Date: Wed, 16 Apr 2025 15:17:59 -0300 [thread overview]
Message-ID: <20250416181759.GF493866@ziepe.ca> (raw)
In-Reply-To: <67fff12d.650a0220.208c7c.d69dSMTPIN_ADDED_BROKEN@mx.google.com>
On Wed, Apr 16, 2025 at 11:04:27AM -0700, Jacob Pan wrote:
> Per last discussion "SMMU driver have a list of potential addresses and
> select the first one that does not intersect with the non-working IOVA
> ranges.". If we don't know what the "non-working IOVA" is, how do we
> know it does not intersect the "potential addresses"?
I had understood from previous discussions that this platform is
properly creating IOMMU_RESV_RESERVED regions for the IOVA that
doesn't work. Otherwise everything is broken..
Presumably that happens through iommu_dma_get_resv_regions() calling
of_iommu_get_resv_regions() on a DT platform. There is a schema
describing how to do this, so platform firmware should be able to do it..
So the fix seems trivial enough to me:
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 b4c21aaed1266a..ebba18579151bc 100644
--- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
+++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
@@ -3562,17 +3562,29 @@ static int arm_smmu_of_xlate(struct device *dev,
static void arm_smmu_get_resv_regions(struct device *dev,
struct list_head *head)
{
- struct iommu_resv_region *region;
- int prot = IOMMU_WRITE | IOMMU_NOEXEC | IOMMU_MMIO;
-
- region = iommu_alloc_resv_region(MSI_IOVA_BASE, MSI_IOVA_LENGTH,
- prot, IOMMU_RESV_SW_MSI, GFP_KERNEL);
- if (!region)
- return;
-
- list_add_tail(®ion->list, head);
+ static const u64 msi_bases[] = { MSI_IOVA_BASE, 0x12340000 };
iommu_dma_get_resv_regions(dev, head);
+
+ /*
+ * Use the first msi_base that does not intersect with a platform
+ * reserved region. The SW MSI base selection is entirely arbitary.
+ */
+ for (i = 0; i != ARRAY_SIZE(msi_bases); i++) {
+ struct iommu_resv_region *region;
+
+ if (resv_intersects(msi_bases[i], MSI_IOVA_LENGTH))
+ continue;
+
+ region = iommu_alloc_resv_region(msi_bases[i], MSI_IOVA_LENGTH,
+ IOMMU_WRITE | IOMMU_NOEXEC |
+ IOMMU_MMIO,
+ IOMMU_RESV_SW_MSI, GFP_KERNEL);
+ if (!region)
+ return;
+ list_add_tail(®ion->list, head);
+ return;
+ }
}
static int arm_smmu_dev_enable_feature(struct device *dev,
Jason
next prev parent reply other threads:[~2025-04-16 18:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 22:50 [PATCH v2 0/3] arm-smmu: select suitable IOVA Shyam Saini
2025-04-10 22:50 ` [PATCH v2 1/3] arm-smmu: move MSI_IOVA macro definitions Shyam Saini
2025-04-11 23:28 ` kernel test robot
2025-04-12 3:17 ` kernel test robot
2025-04-10 22:50 ` [PATCH v2 2/3] dt-bindings: iommu: add "arm,smmu-faulty-msi-iova" property Shyam Saini
2025-04-10 22:50 ` [PATCH v2 3/3] arm-smmu: select suitable MSI IOVA Shyam Saini
2025-04-11 23:40 ` kernel test robot
2025-04-10 23:00 ` [PATCH v2 0/3] arm-smmu: select suitable IOVA Jason Gunthorpe
2025-04-16 18:04 ` Jacob Pan
[not found] ` <67fff12d.650a0220.208c7c.d69dSMTPIN_ADDED_BROKEN@mx.google.com>
2025-04-16 18:17 ` Jason Gunthorpe [this message]
2025-04-16 21:34 ` Jacob Pan
2025-05-20 22:42 ` Shyam Saini
2025-05-25 19:07 ` Jason Gunthorpe
2025-05-27 20:54 ` Shyam Saini
2025-05-28 0:04 ` Jason Gunthorpe
2025-05-28 22:42 ` Jacob Pan
[not found] ` <68379171.170a0220.191ee0.8d6bSMTPIN_ADDED_BROKEN@mx.google.com>
2025-05-29 0:38 ` Jason Gunthorpe
2025-05-29 18:22 ` Shyam Saini
2025-05-29 18:38 ` Jason Gunthorpe
2025-05-29 22:08 ` Shyam Saini
2025-05-30 13:13 ` Jason Gunthorpe
2025-05-30 21:30 ` Shyam Saini
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=20250416181759.GF493866@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=code@tyhicks.com \
--cc=devicetree@vger.kernel.org \
--cc=eahariha@linux.microsoft.com \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=jacob.pan@linux.microsoft.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=shyamsaini@linux.microsoft.com \
--cc=vijayb@linux.microsoft.com \
--cc=virtualization@lists.linux.dev \
--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).