From: Christoph Hellwig <hch@lst.de>
To: Rob Clark <robdclark@chromium.org>
Cc: Kate Stewart <kstewart@linuxfoundation.org>,
Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
Eric Biggers <ebiggers@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Imre Deak <imre.deak@intel.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Chris Wilson <chris@chris-wilson.co.uk>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Will Deacon <will@kernel.org>, Christoph Hellwig <hch@lst.de>,
Emil Velikov <emil.velikov@collabora.com>,
Deepak Sharma <deepak.sharma@amd.com>,
Paul Burton <paul.burton@mips.com>,
Mike Rapoport <rppt@linux.ibm.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"moderated list:ARM64 PORT \(AARCH64 ARCHITECTURE\)"
<linux-arm-kernel@lists.infradead.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
"open list:MIPS" <linux-mips@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Robin Murphy <robin.murphy@arm.com>,
"open list:DRM DRIVER FOR MSM ADRENO GPU"
<linux-arm-msm@vger.kernel.org>, Joerg Roedel <jroedel@suse.de>,
Arnd Bergmann <arnd@arndb.de>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Hauke Mehrtens <hauke@hauke-m.de>,
Jesper Dangaard Brouer <brouer@redhat.com>,
"Wolfram Sang \(Renesas\)" <wsa+renesas@sang-engineering.com>,
"open list:LINUX FOR POWERPC \(32-BIT AND 64-BIT\)"
<linuxppc-dev@lists.ozlabs.org>,
Alexios Zavras <alexios.zavras@intel.com>,
Russell King <rmk+kernel@armlinux.org.uk>,
Doug Anderson <armlinux@m.disordat.com>,
Thomas Gleixner <tglx@linutronix.de>, Sean Paul <sean@poorly.run>,
Allison Randal <allison@lohutok.net>,
Enrico Weigelt <info@metux.net>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
open list <linux-kernel@vger.kernel.org>,
Rob Clark <robdclark@gmail.com>,
Souptick Joarder <jrdr.linux@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"open list:DRM DRIVER FOR MSM ADRENO GPU"
<freedreno@lists.freedesktop.org>,
christian.koenig@amd.com
Subject: Re: [PATCH 0/6] drm+dma: cache support for arm, etc
Date: Mon, 19 Aug 2019 07:23:37 +0200 [thread overview]
Message-ID: <20190819052337.GA16622@lst.de> (raw)
In-Reply-To: <CAJs_Fx6am7TeDFSG=CcTT=4KwhqrZX_jnn56NaWcDkGVizuakg@mail.gmail.com>
On Fri, Aug 16, 2019 at 02:04:35PM -0700, Rob Clark wrote:
> I don't disagree about needing an API to get uncached memory (or
> ideally just something outside of the linear map). But I think this
> is a separate problem.
>
> What I was hoping for, for v5.4, is a way to stop abusing dma_map/sync
> for cache ops to get rid of the hack I had to make for v5.3. And also
> to fix vgem on non-x86. (Unfortunately changing vgem to used cached
> mappings breaks x86 CI, but fixes CI on arm/arm64..) We can do that
> without any changes in allocation. There is still the possibility for
> problems due to cached alias, but that has been a problem this whole
> time, it isn't something new.
But that just means we start exposing random low-level APIs that
people will quickly abuse.. In fact even your simple plan to some
extent already is an abuse of the intent of these functions, and
it also requires a lot of knowledge in the driver that in the normal
cases drivers can't know (e.g. is the device dma coherent or not).
next prev parent reply other threads:[~2019-08-19 5:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 21:59 [PATCH 0/6] drm+dma: cache support for arm, etc Rob Clark
2019-08-14 21:59 ` [PATCH 3/6] powerpc: export arch_sync_dma_for_*() Rob Clark
2019-08-15 6:51 ` [PATCH 0/6] drm+dma: cache support for arm, etc Christoph Hellwig
2019-08-15 13:54 ` Rob Clark
2019-08-15 17:53 ` Christoph Hellwig
2019-08-15 18:21 ` Koenig, Christian
2019-08-15 18:27 ` Christoph Hellwig
2019-08-16 21:04 ` Rob Clark
2019-08-19 5:23 ` Christoph Hellwig [this message]
2019-08-19 14:39 ` Rob Clark
2019-08-15 18:48 Koenig, Christian
2019-08-15 18:52 ` Christoph Hellwig
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=20190819052337.GA16622@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=alexios.zavras@intel.com \
--cc=allison@lohutok.net \
--cc=anshuman.khandual@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=armlinux@m.disordat.com \
--cc=arnd@arndb.de \
--cc=benjamin.gaignard@linaro.org \
--cc=brouer@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=chris@chris-wilson.co.uk \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=deepak.sharma@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ebiggers@google.com \
--cc=emil.velikov@collabora.com \
--cc=freedreno@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=hauke@hauke-m.de \
--cc=imre.deak@intel.com \
--cc=info@metux.net \
--cc=jrdr.linux@gmail.com \
--cc=jroedel@suse.de \
--cc=kstewart@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.mizuma@jp.fujitsu.com \
--cc=macro@linux-mips.org \
--cc=mchehab+samsung@kernel.org \
--cc=paul.burton@mips.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=robdclark@chromium.org \
--cc=robdclark@gmail.com \
--cc=robin.murphy@arm.com \
--cc=rppt@linux.ibm.com \
--cc=sean@poorly.run \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yamada.masahiro@socionext.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).