From: Boris Brezillon <boris.brezillon@collabora.com>
To: Steven Price <steven.price@arm.com>
Cc: robh@kernel.org, tomeu.vizoso@collabora.com,
narmstrong@baylibre.com, khilman@baylibre.com,
Robin Murphy <robin.murphy@arm.com>,
dri-devel@lists.freedesktop.org,
iommu@lists.linux-foundation.org,
alyssa.rosenzweig@collabora.com,
linux-amlogic@lists.infradead.org, will@kernel.org,
linux-arm-kernel@lists.infradead.org, jbrunet@baylibre.com
Subject: Re: [PATCH v2 1/3] iommu/io-pgtable-arm: Support coherency for Mali LPAE
Date: Mon, 5 Oct 2020 17:52:47 +0200 [thread overview]
Message-ID: <20201005175247.002bf8f0@collabora.com> (raw)
In-Reply-To: <07c4b74f-c87b-092c-3fc7-c005c8c65206@arm.com>
On Mon, 5 Oct 2020 16:16:32 +0100
Steven Price <steven.price@arm.com> wrote:
> On 05/10/2020 15:50, Boris Brezillon wrote:
> > On Tue, 22 Sep 2020 15:16:48 +0100
> > Robin Murphy <robin.murphy@arm.com> wrote:
> >
> >> Midgard GPUs have ACE-Lite master interfaces which allows systems to
> >> integrate them in an I/O-coherent manner. It seems that from the GPU's
> >> viewpoint, the rest of the system is its outer shareable domain, and so
> >> even when snoop signals are wired up, they are only emitted for outer
> >> shareable accesses. As such, setting the TTBR_SHARE_OUTER bit does
> >> indeed get coherent pagetable walks working nicely for the coherent
> >> T620 in the Arm Juno SoC.
> >>
> >> Reviewed-by: Steven Price <steven.price@arm.com>
> >> Tested-by: Neil Armstrong <narmstrong@baylibre.com>
> >> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> >> ---
> >> drivers/iommu/io-pgtable-arm.c | 11 ++++++++++-
> >> 1 file changed, 10 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/iommu/io-pgtable-arm.c b/drivers/iommu/io-pgtable-arm.c
> >> index dc7bcf858b6d..b4072a18e45d 100644
> >> --- a/drivers/iommu/io-pgtable-arm.c
> >> +++ b/drivers/iommu/io-pgtable-arm.c
> >> @@ -440,7 +440,13 @@ static arm_lpae_iopte arm_lpae_prot_to_pte(struct arm_lpae_io_pgtable *data,
> >> << ARM_LPAE_PTE_ATTRINDX_SHIFT);
> >> }
> >>
> >> - if (prot & IOMMU_CACHE)
> >> + /*
> >> + * Also Mali has its own notions of shareability wherein its Inner
> >> + * domain covers the cores within the GPU, and its Outer domain is
> >> + * "outside the GPU" (i.e. either the Inner or System domain in CPU
> >> + * terms, depending on coherency).
> >> + */
> >> + if (prot & IOMMU_CACHE && data->iop.fmt != ARM_MALI_LPAE)
> >> pte |= ARM_LPAE_PTE_SH_IS;
> >> else
> >> pte |= ARM_LPAE_PTE_SH_OS;
> >
> > Actually, it still doesn't work on s922x :-/. For it to work I
> > correctly, I need to drop the outer shareable flag here.
>
> The logic here does seem a bit odd. Originally it was:
>
> IOMMU_CACHE -> Inner shared (value 3)
> !IOMMU_CACHE -> Outer shared (value 2)
>
> For Mali we're forcing everything to the second option. But Mali being
> Mali doesn't do things the same as LPAE, so for Mali we have:
>
> 0 - not shared
> 1 - reserved
> 2 - inner(*) and outer shareable
> 3 - inner shareable only
>
> (*) where "inner" means internal to the GPU, and "outer" means shared
> with the CPU "inner". Very confusing!
>
> So originally we had:
> IOMMU_CACHE -> not shared with CPU (only internally in the GPU)
> !IOMMU_CACHE -> shared with CPU
>
> The change above gets us to "always shared", dropping the SH_OS bit
> would get us to not even shareable between cores (which doesn't sound
> like what we want).
Thanks for this explanation.
>
> It's not at all clear to me why the change helps, but I suspect we want
> at least "inner" shareable.
Right. Looks like all this was caused by a bad conflict resolution
during a rebase. Sorry for the noise :-/.
_______________________________________________
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:[~2020-10-05 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 14:16 [PATCH v2 0/3] drm: panfrost: Coherency support Robin Murphy
2020-09-22 14:16 ` [PATCH v2 1/3] iommu/io-pgtable-arm: Support coherency for Mali LPAE Robin Murphy
2020-09-28 14:59 ` Will Deacon
2020-10-05 14:50 ` Boris Brezillon
2020-10-05 15:16 ` Steven Price
2020-10-05 15:52 ` Boris Brezillon [this message]
2020-09-22 14:16 ` [PATCH v2 2/3] drm/panfrost: Support cache-coherent integrations Robin Murphy
2020-09-22 14:16 ` [PATCH v2 3/3] arm64: dts: meson: Describe G12b GPU as coherent Robin Murphy
2020-09-22 16:25 ` [PATCH v2 0/3] drm: panfrost: Coherency support Alyssa Rosenzweig
2020-10-30 8:35 ` Neil Armstrong
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=20201005175247.002bf8f0@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=alyssa.rosenzweig@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=narmstrong@baylibre.com \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=steven.price@arm.com \
--cc=tomeu.vizoso@collabora.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).