All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolin Chen <nicolinc@nvidia.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Peng Fan <peng.fan@oss.nxp.com>, <will@kernel.org>,
	<joro@8bytes.org>, <jpb@kernel.org>, <jgg@ziepe.ca>,
	<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>, <peng.fan@nxp.com>
Subject: Re: [PATCH RFC v2 2/4] iommu/arm-smmu-v3: Support shared SIDs in insert/remove_master
Date: Tue, 22 Sep 2026 10:47:02 -0700	[thread overview]
Message-ID: <arK/FoWsg5qJ7G3T@nvidia.com> (raw)
In-Reply-To: <31be5621-92f6-4101-898f-806335d56155@arm.com>

On Tue, Sep 22, 2026 at 04:52:35PM +0100, Robin Murphy wrote:
> On 22/09/2026 3:13 pm, Peng Fan wrote:
> > On Mon, Sep 21, 2026 at 04:15:18PM -0700, Nicolin Chen wrote:
> > > Does i.MX need to support SID-sharing with multi-SD device? If not,
> > > the master could have only a simple shared_masters_elm:
> > 
> > For i.MX, there is no need to support SID sharing for multi-SID device for now.
> > Not sure, in future there are cases that needs SID sharing for multi-SID device.
> 
> I have a system meeting those conditions :)
> 
> Specifically, I have a physical PCIe-to-PCI bridge board with a couple of
> ancient cards plugged into it (such that they each end up with their own RID
> plus the common bridge alias RID) just in case I ever got round to looking
> at this myself...

Though in such cases we cannot reject num_streams != 1 any more,
that bridge can still end up with one single shared stream, e.g.
 alias  = PCI_DEVID(0x02, PCI_DEVFN(0,0)) = 0x0200
 Card A = 02:01.0 -> sorted SIDs { 0x0200, 0x0208 }
 Card B = 02:02.0 -> sorted SIDs { 0x0200, 0x0210 }
?

Hopefully, we won't have to support an ancient PCIe-to-PCI bridge
connecting with another ancient PCI-to-PCI bridge...

Nicolin

  reply	other threads:[~2026-09-22 17:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 11:34 [PATCH RFC v2 0/4] iommu/arm-smmu-v3: Support shared Stream IDs Peng Fan (OSS)
2026-09-21 11:35 ` [PATCH RFC v2 1/4] iommu/arm-smmu-v3: Convert streams from RB tree to XArray Peng Fan (OSS)
2026-09-21 19:24   ` Nicolin Chen
2026-09-22 14:04     ` Peng Fan
2026-09-22 16:56       ` Nicolin Chen
2026-09-21 12:38 ` [PATCH RFC v2 2/4] iommu/arm-smmu-v3: Support shared SIDs in insert/remove_master Peng Fan (OSS)
2026-09-21 23:15   ` Nicolin Chen
2026-09-22 14:13     ` Peng Fan
2026-09-22 15:52       ` Robin Murphy
2026-09-22 17:47         ` Nicolin Chen [this message]
2026-09-21 12:40 ` [PATCH RFC v2 3/4] iommu/arm-smmu-v3: Group aliasing devices into the same IOMMU group Peng Fan (OSS)
2026-09-21 12:41 ` [PATCH RFC v2 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=arK/FoWsg5qJ7G3T@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.