From: Mostafa Saleh <smostafa@google.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, will@kernel.org,
joro@8bytes.org, jean-philippe@linaro.org, nicolinc@nvidia.com,
mshavit@google.com
Subject: Re: [PATCH v2] iommu/arm-smmu-v3: Match Stall behaviour for S2
Date: Fri, 16 Aug 2024 09:49:22 +0000 [thread overview]
Message-ID: <Zr8gom978iZftV_9@google.com> (raw)
In-Reply-To: <20240815135951.GM3468552@ziepe.ca>
On Thu, Aug 15, 2024 at 10:59:51AM -0300, Jason Gunthorpe wrote:
> On Thu, Aug 15, 2024 at 02:41:52PM +0100, Robin Murphy wrote:
>
> > Unfortunately we can't do that, because there *are* RCiEP devices whose data
> > interfaces are native AMBA, and thus for whom stalling is not actually a
> > protocol violation as it would be on a real PCIe transport layer;
> > correspondingly, it's *because* they are not true PCIe devices that they
> > can't support ATS, and thus need stall support in order to do SVA, so things
> > should still work out OK in practice.
>
> I wondered if that would be the case.
>
> Looks like if we want to do anything then arm_smmu_ats_supported()
> would be the right place.
Yes, I guess that might be the place, although the spec seems more
relaxed regarding stage-1 stall.
Anyway I will drop it from this patch, as Robin mentioned this should
only happen with buggy firmware and we can have another patch to
harden that if required.
Thanks,
Mostafa
>
> > > if (dev_is_pci(dev)) {
> > >
> > > Though I have no idea how the GPU driver that wants to use this
> > > works - it doesn't seem to be intree :\
> >
> > It's not a GPU: drivers/crypto/hisilicon/zip/
>
> Ohhhh.. so it goes through uacce, I see.
>
> Jason
prev parent reply other threads:[~2024-08-16 9:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 14:56 [PATCH v2] iommu/arm-smmu-v3: Match Stall behaviour for S2 Mostafa Saleh
2024-08-14 15:51 ` Jason Gunthorpe
2024-08-15 11:30 ` Mostafa Saleh
2024-08-15 12:05 ` Jason Gunthorpe
2024-08-15 12:16 ` Robin Murphy
2024-08-15 12:26 ` Mostafa Saleh
2024-08-15 12:59 ` Jason Gunthorpe
2024-08-15 13:41 ` Robin Murphy
2024-08-15 13:59 ` Jason Gunthorpe
2024-08-16 9:49 ` Mostafa Saleh [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=Zr8gom978iZftV_9@google.com \
--to=smostafa@google.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mshavit@google.com \
--cc=nicolinc@nvidia.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;
as well as URLs for NNTP newsgroup(s).