From: Jason Gunthorpe <jgg@ziepe.ca>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Peng Fan <peng.fan@nxp.com>,
"eric.auger@redhat.com" <eric.auger@redhat.com>,
"jean-philippe.brucker@arm.com" <jean-philippe.brucker@arm.com>,
"will@kernel.org" <will@kernel.org>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: arm-smmu-v3 sharing SID
Date: Thu, 18 May 2023 09:36:53 -0300 [thread overview]
Message-ID: <ZGYb5Y1eAgvt/TdY@ziepe.ca> (raw)
In-Reply-To: <359b01bc-e87a-9a50-c971-681e89985491@arm.com>
On Thu, May 18, 2023 at 12:33:25PM +0100, Robin Murphy wrote:
> I'm fairly confident in reasoning about this for basic .attach_dev purposes,
> since I did implement the equivalent for SMMUv2, but I'm not sure I even
> want to think about what it would mean for SVA, PASIDs and nesting...
IIRC we've already taken the approach elsewhere to block PASID if the
group is not singleton.
Jason
prev parent reply other threads:[~2023-05-18 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 10:46 arm-smmu-v3 sharing SID Peng Fan
2023-05-18 11:33 ` Robin Murphy
2023-05-18 11:44 ` Peng Fan
2023-05-18 13:04 ` Jean-Philippe Brucker
2023-05-19 2:49 ` Baolu Lu
2023-05-18 12:36 ` Jason Gunthorpe [this message]
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=ZGYb5Y1eAgvt/TdY@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe.brucker@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=peng.fan@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