From: Mostafa Saleh <smostafa@google.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
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: Thu, 15 Aug 2024 12:26:46 +0000 [thread overview]
Message-ID: <Zr30BjAcVDKJPv3B@google.com> (raw)
In-Reply-To: <91d6574d-c67e-484c-ad96-91c9fd3d0c43@arm.com>
Hi Robin,
On Thu, Aug 15, 2024 at 01:16:19PM +0100, Robin Murphy wrote:
> On 15/08/2024 12:30 pm, Mostafa Saleh wrote:
> > Hi Jason,
> >
> > On Wed, Aug 14, 2024 at 12:51:51PM -0300, Jason Gunthorpe wrote:
> > > On Wed, Aug 14, 2024 at 02:56:33PM +0000, Mostafa Saleh wrote:
> > >
> > > > Also described in the pseudocode “SteIllegal()”
> > > > if eff_idr0_stall_model == '10' && STE.S2S == '0' then
> > > > // stall_model forcing stall, but S2S == 0
> > > > return TRUE;
> > >
> > > This clips out an important bit:
> > >
> > > if STE.Config == '11x' then
> > > [..]
> > > if eff_idr0_stall_model == '10' && STE.S2S == '0' then
> > > // stall_model forcing stall, but S2S == 0
> > > return TRUE;
> > >
> > > And here we are using STRTAB_STE_0_CFG_S1_TRANS which is 101 and won't
> > > match the STE.Config qualification.
> > >
> > > The plain text language said the S2S is only required if the S2 is
> > > translating, STRTAB_STE_0_CFG_S1_TRANS puts it in bypass.
> >
> > Yes, my bad, this should be for stage-2 only which is populated in
> > arm_smmu_make_s2_domain_ste()
> >
> > >
> > > > + /*
> > > > + * S2S is ignored if stage-2 exists but not enabled.
> > > > + * S2S is not compatible with ATS.
> > > > + */
> > > > + if (master->stall_enabled && !ats_enabled &&
> > > > + smmu->features & ARM_SMMU_FEAT_TRANS_S2)
> > > > + target->data[2] |= STRTAB_STE_2_S2S;
> > >
> > > We can't ignore ATS if it was requested here.
>
> I don't see much value in adding effectively-dead checks for something which
> is already forbidden by the architecture. The definition of STALL_MODEL
> explicitly states:
>
> "An SMMU associated with a PCI system must not have STALL_MODEL == 0b10".
>
Ah, I was expecting that as otherwise it's contradiction, but couldn't
find it while searching. Thanks for pointing it out, I will drop all
references to ATS then.
Thanks,
Mostafa
> Thanks,
> Robin.
next prev parent reply other threads:[~2024-08-15 12:27 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 [this message]
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
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=Zr30BjAcVDKJPv3B@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).