From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "Koenig, Christian" <christian.koenig@amd.com>
Cc: Will Deacon <will.deacon@arm.com>,
Carsten Haitzler <Carsten.Haitzler@arm.com>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Michael Ellerman <mpe@ellerman.id.au>,
David Airlie <airlied@linux.ie>,
"Daenzer, Michel" <Michel.Daenzer@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Christoph Hellwig <hch@infradead.org>,
"Zhang, Jerry" <Jerry.Zhang@amd.com>,
"Huang, Ray" <Ray.Huang@amd.com>,
amd-gfx list <amd-gfx@lists.freedesktop.org>,
Alex Deucher <alexdeucher@gmail.com>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
Sean Paul <sean@poorly.run>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH] drm: enable uncached DMA optimization for ARM and arm64
Date: Fri, 25 Jan 2019 12:35:15 +0100 [thread overview]
Message-ID: <CAKv+Gu_faPAf+0NBTNM03EUH4-_0vWbPfDQneshps5vbaU4R_Q@mail.gmail.com> (raw)
In-Reply-To: <961e758d-b0a0-8f6c-a8fa-c3047e058706@gmail.com>
On Fri, 25 Jan 2019 at 12:30, Christian König
<ckoenig.leichtzumerken@gmail.com> wrote:
>
> Am 25.01.19 um 09:43 schrieb Ard Biesheuvel:
> > On Thu, 24 Jan 2019 at 15:01, Alex Deucher <alexdeucher@gmail.com> wrote:
> >> On Thu, Jan 24, 2019 at 9:00 AM Ard Biesheuvel
> >> <ard.biesheuvel@linaro.org> wrote:
> >>> On Thu, 24 Jan 2019 at 13:31, Koenig, Christian
> >>> <Christian.Koenig@amd.com> wrote:
> >>>> Am 24.01.19 um 13:06 schrieb Ard Biesheuvel:
> >>>>> The DRM driver stack is designed to work with cache coherent devices
> >>>>> only, but permits an optimization to be enabled in some cases, where
> >>>>> for some buffers, both the CPU and the GPU use uncached mappings,
> >>>>> removing the need for DMA snooping and allocation in the CPU caches.
> >>>>>
> >>>>> The use of uncached GPU mappings relies on the correct implementation
> >>>>> of the PCIe NoSnoop TLP attribute by the platform, otherwise the GPU
> >>>>> will use cached mappings nonetheless. On x86 platforms, this does not
> >>>>> seem to matter, as uncached CPU mappings will snoop the caches in any
> >>>>> case. However, on ARM and arm64, enabling this optimization on a
> >>>>> platform where NoSnoop is ignored results in loss of coherency, which
> >>>>> breaks correct operation of the device. Since we have no way of
> >>>>> detecting whether NoSnoop works or not, just disable this
> >>>>> optimization entirely for ARM and arm64.
> >>>>>
> >>>>> Cc: Christian Koenig <christian.koenig@amd.com>
> >>>>> Cc: Alex Deucher <alexander.deucher@amd.com>
> >>>>> Cc: David Zhou <David1.Zhou@amd.com>
> >>>>> Cc: Huang Rui <ray.huang@amd.com>
> >>>>> Cc: Junwei Zhang <Jerry.Zhang@amd.com>
> >>>>> Cc: Michel Daenzer <michel.daenzer@amd.com>
> >>>>> Cc: David Airlie <airlied@linux.ie>
> >>>>> Cc: Daniel Vetter <daniel@ffwll.ch>
> >>>>> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> >>>>> Cc: Maxime Ripard <maxime.ripard@bootlin.com>
> >>>>> Cc: Sean Paul <sean@poorly.run>
> >>>>> Cc: Michael Ellerman <mpe@ellerman.id.au>
> >>>>> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> >>>>> Cc: Will Deacon <will.deacon@arm.com>
> >>>>> Cc: Christoph Hellwig <hch@infradead.org>
> >>>>> Cc: Robin Murphy <robin.murphy@arm.com>
> >>>>> Cc: amd-gfx list <amd-gfx@lists.freedesktop.org>
> >>>>> Cc: dri-devel <dri-devel@lists.freedesktop.org>
> >>>>> Reported-by: Carsten Haitzler <Carsten.Haitzler@arm.com>
> >>>>> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> >>>> The subject line should probably read "disable uncached...".
> >>>>
> >>> Ugh, of course ...
> >>>
> >>>> With that fixed the patch is Reviewed-by: Christian König
> >>>> <christian.koenig@amd.com>.
> >>>>
> >> Same:
> >> Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
> >>
> > Thanks all
> >
> > Should I resend the patch with the subject corrected?
>
> I will update the subject line and push it upstream through
> drm-misc-next if nobody objects.
>
Wonderful, thanks.
_______________________________________________
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:[~2019-01-25 11:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 12:06 [PATCH] drm: enable uncached DMA optimization for ARM and arm64 Ard Biesheuvel
2019-01-24 12:31 ` Koenig, Christian
2019-01-24 12:32 ` Ard Biesheuvel
2019-01-24 14:01 ` Alex Deucher
2019-01-25 8:43 ` Ard Biesheuvel
2019-01-25 11:30 ` Christian König
2019-01-25 11:35 ` Ard Biesheuvel [this message]
2019-02-06 17:23 ` Ard Biesheuvel
2019-02-06 18:38 ` Christian König
2019-02-07 15:20 ` Ard Biesheuvel
2019-02-07 15:33 ` Alex Deucher
2019-02-07 16:01 ` Ard Biesheuvel
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=CAKv+Gu_faPAf+0NBTNM03EUH4-_0vWbPfDQneshps5vbaU4R_Q@mail.gmail.com \
--to=ard.biesheuvel@linaro.org \
--cc=Alexander.Deucher@amd.com \
--cc=Carsten.Haitzler@arm.com \
--cc=Jerry.Zhang@amd.com \
--cc=Michel.Daenzer@amd.com \
--cc=Ray.Huang@amd.com \
--cc=airlied@linux.ie \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@bootlin.com \
--cc=mpe@ellerman.id.au \
--cc=robin.murphy@arm.com \
--cc=sean@poorly.run \
--cc=will.deacon@arm.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).