From: Nicolin Chen <nicolinc@nvidia.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
"Joerg Roedel (AMD)" <joro@8bytes.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
Jean-Philippe Brucker <jpb@kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH RFC v4 2/4] iommu/arm-smmu-v3: Support shared SIDs in insert/remove_master
Date: Thu, 1 Oct 2026 10:17:22 -0700 [thread overview]
Message-ID: <ar6Vou12yzoZ2z8I@nvidia.com> (raw)
In-Reply-To: <20261001-smmu-shared-sid-ver3-v4-2-06b34fb2e691@nxp.com>
On Thu, Oct 01, 2026 at 08:49:59PM +0800, Peng Fan (OSS) wrote:
> -static int arm_smmu_streams_cmp_node(struct rb_node *lhs,
> - const struct rb_node *rhs)
> +static int arm_smmu_streams_cmp_node(struct rb_node *lhs, const struct rb_node *rhs)
Why is this changed?
> @@ -4136,23 +4151,33 @@ static int arm_smmu_insert_master(struct arm_smmu_device *smmu,
> existing = rb_find_add(&new_stream->node, &smmu->streams,
> arm_smmu_streams_cmp_node);
> if (existing) {
> - struct arm_smmu_master *existing_master =
> - rb_entry(existing, struct arm_smmu_stream, node)
> - ->master;
> + struct arm_smmu_stream *existing_stream =
> + rb_entry(existing, struct arm_smmu_stream, node);
>
> /* Bridged PCI devices may end up with duplicated IDs */
> - if (existing_master == master)
> + if (existing_stream->master == master)
> continue;
>
> - dev_warn(master->dev,
> - "Aliasing StreamID 0x%x (from %s) unsupported, expect DMA to be broken\n",
> - sid, dev_name(existing_master->dev));
> - ret = -ENODEV;
> - break;
> + if (master->num_streams != 1 ||
> + existing_stream->master->num_streams != 1) {
> + dev_warn(master->dev,
> + "Shared StreamID 0x%x not supported for multi-SID masters\n",
> + sid);
> + ret = -ENODEV;
> + break;
> + }
> +
> + if (list_empty(&existing_stream->shared_masters))
> + list_add_tail(&existing_stream->master->shared_masters_elm,
> + &existing_stream->shared_masters);
> + list_add_tail(&master->shared_masters_elm,
> + &existing_stream->shared_masters);
Masters still hold duplicated streams for the shared SID. And their
ste_installed flags are out of sync..
master_a->stream[0]->a's stream0 {ste_installed=true}
master_b->stream[0]->b's stream0 {ste_installed=false}
What I have been suggesting is to have a shared stream:
master_a->stream[0]-->shared stream0 {ste_installed=true}
master_b->stream[0]-|
So, the driver would need a rework first changing master:
- struct arm_smmu_stream *streams;
+ struct arm_smmu_stream **streams;
Also, arm_smmu_insert_master() needs to reverse its allocation:
for (i = 0; i < fwspec->num_ids; i++) {
stream = arm_smmu_find_stream(smmu, sid);
if (stream) {
// link to the existing stream
} else {
// allocate new stream
}
master->streams[i] = stream;
}
if (!ret)
sort();
Nicolin
next prev parent reply other threads:[~2026-10-01 17:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 12:49 [PATCH RFC v4 0/4] iommu/arm-smmu-v3: Support shared Stream IDs Peng Fan (OSS)
2026-10-01 12:49 ` [PATCH RFC v4 1/4] iommu/arm-smmu-v3: Skip duplicate SIDs when erasing streams from RB tree Peng Fan (OSS)
2026-10-01 16:07 ` Nicolin Chen
2026-10-02 10:19 ` Peng Fan
2026-10-01 12:49 ` [PATCH RFC v4 2/4] iommu/arm-smmu-v3: Support shared SIDs in insert/remove_master Peng Fan (OSS)
2026-10-01 17:17 ` Nicolin Chen [this message]
2026-10-02 10:27 ` Peng Fan
2026-10-01 12:50 ` [PATCH RFC v4 3/4] iommu/arm-smmu-v3: Group aliasing devices into the same IOMMU group Peng Fan (OSS)
2026-10-01 12:50 ` [PATCH RFC v4 4/4] iommu/arm-smmu-v3: Wire up shared-SID STE ordering and feature gating Peng Fan (OSS)
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=ar6Vou12yzoZ2z8I@nvidia.com \
--to=nicolinc@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=jpb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.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
all inboxes | Powered by JetHome®