From: Jason Gunthorpe <jgg@nvidia.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Nicolin Chen <nicolinc@nvidia.com>,
will@kernel.org, joro@8bytes.org,
shameerali.kolothum.thodi@huawei.com, yangyicong@hisilicon.com,
jean-philippe@linaro.org, linux-arm-kernel@lists.infradead.org,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] iommu/arm-smmu-v3: Allow default substream bypass with a pasid support
Date: Wed, 28 Jun 2023 12:43:25 -0300 [thread overview]
Message-ID: <ZJxVHf2YZ1LxPx23@nvidia.com> (raw)
In-Reply-To: <2274ba47-7def-082c-8429-8f2cc18adf9f@arm.com>
On Wed, Jun 28, 2023 at 04:39:48PM +0100, Robin Murphy wrote:
> > I'd try keeping most of the parts intact while adding a pointer
> > to a structure holding pagetable stuff, to make it cleaner. Then
> > the S1DSS bypass case can be flagged by an empty pointer.
>
> I'd expect that what you need for this is much the same as what Michael has
> already proposed for the PASID-generalisation series. The current inside-out
> notion of S1 domains owning CD tables is what's getting in the way of doing
> the right thing cleanly, in both cases.
Yeah, that was sort of my guessed feeling as well..
What do you think of Michael's series?
Jason
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-06-28 15:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 3:33 [PATCH v1] iommu/arm-smmu-v3: Allow default substream bypass with a pasid support Nicolin Chen
2023-06-27 9:00 ` Robin Murphy
2023-06-27 17:06 ` Nicolin Chen
2023-06-27 23:29 ` Robin Murphy
2023-06-28 0:13 ` Nicolin Chen
2023-06-28 15:39 ` Robin Murphy
2023-06-28 15:43 ` Jason Gunthorpe [this message]
2023-06-28 15:59 ` Nicolin Chen
2023-09-12 22:13 ` Aahil Awatramani
2023-09-14 1:02 ` Nicolin Chen
2023-09-14 9:01 ` Michael Shavit
2023-09-14 10:26 ` Nicolin Chen
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=ZJxVHf2YZ1LxPx23@nvidia.com \
--to=jgg@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.com \
/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).