From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: "Koenig, Christian" <Christian.Koenig-5C7GfCeVMHo@public.gmane.org>
Cc: Kate Stewart
<kstewart-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
Masayoshi Mizuma
<m.mizuma-+CUm20s59erQFUHtdCDX3A@public.gmane.org>,
"Maciej W. Rozycki"
<macro-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org>,
Eric Biggers <ebiggers-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
Imre Deak <imre.deak-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
dri-devel
<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
Chris Wilson
<chris-Y6uKTt2uX1cEflXRtASbqLVCufUGDwFn@public.gmane.org>,
Masahiro Yamada
<yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.org>,
Benjamin Gaignard
<benjamin.gaignard-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Mauro Carvalho Chehab
<mchehab+samsung-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Will Deacon <will-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
Emil Velikov
<emil.velikov-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>,
Rob Clark <robdclark-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
Michael Ellerman <mpe-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org>,
Paul Burton <paul.burton-8NJIiSa5LzA@public.gmane.org>,
Mike Rapoport <rppt-tEXmvtCZX7AybS5Ee8rs3A@public.gmane.org>,
Geert Uytterhoeven
<geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>,
"moderated list:ARM64 PORT (AARCH64 ARCHITECTURE)"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Daniel
Subject: Re: [PATCH 0/6] drm+dma: cache support for arm, etc
Date: Thu, 15 Aug 2019 20:52:00 +0200 [thread overview]
Message-ID: <20190815185200.GA21407@lst.de> (raw)
In-Reply-To: <215e5cb7-0fcf-48db-a656-817054dde420-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
On Thu, Aug 15, 2019 at 06:48:39PM +0000, Koenig, Christian wrote:
> Well, for the graphics case I absolutely need to keep the linear kernel mapping. Because for certain use cases the memory is accessed by the kernel all the time as well.
Then don't set DMA_ATTR_NO_KERNEL_MAPPING. At least for x86 and arm64
we should be able to support uncached allocations easily even without
that, and I plan to support that for your use case. But if the driver
is explicitly saying it doesn't want a permanent kernel mapping it makes
sense to (optionally if the architecture can easily do it) unmap the
memory from the kernel linear mapping.
_______________________________________________
Freedreno mailing list
Freedreno@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/freedreno
next prev parent reply other threads:[~2019-08-15 18:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 18:48 [PATCH 0/6] drm+dma: cache support for arm, etc Koenig, Christian
[not found] ` <215e5cb7-0fcf-48db-a656-817054dde420-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2019-08-15 18:52 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-14 21:59 Rob Clark
[not found] ` <20190814220011.26934-1-robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-08-15 6:51 ` Christoph Hellwig
[not found] ` <20190815065117.GA23761-jcswGhMUV9g@public.gmane.org>
2019-08-15 13:54 ` Rob Clark
[not found] ` <CAJs_Fx4bS64s7+xQqsead3N80ZQpofqegFQu+tT=b3wcGd_2pA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-08-15 17:53 ` Christoph Hellwig
[not found] ` <20190815175346.GA19839-jcswGhMUV9g@public.gmane.org>
2019-08-15 18:21 ` Koenig, Christian
[not found] ` <e3f73b3c-49d5-3c19-dfff-0a24b4617e50-5C7GfCeVMHo@public.gmane.org>
2019-08-15 18:27 ` Christoph Hellwig
2019-08-16 21:04 ` Rob Clark
[not found] ` <CAJs_Fx6am7TeDFSG=CcTT=4KwhqrZX_jnn56NaWcDkGVizuakg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-08-19 5:23 ` Christoph Hellwig
[not found] ` <20190819052337.GA16622-jcswGhMUV9g@public.gmane.org>
2019-08-19 14:39 ` Rob Clark
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=20190815185200.GA21407@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=Christian.Koenig-5C7GfCeVMHo@public.gmane.org \
--cc=benjamin.gaignard-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=catalin.marinas-5wv7dgnIgG8@public.gmane.org \
--cc=chris-Y6uKTt2uX1cEflXRtASbqLVCufUGDwFn@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=ebiggers-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=emil.velikov-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \
--cc=geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org \
--cc=imre.deak-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=kstewart-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=m.mizuma-+CUm20s59erQFUHtdCDX3A@public.gmane.org \
--cc=macro-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org \
--cc=mchehab+samsung-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=mpe-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org \
--cc=paul.burton-8NJIiSa5LzA@public.gmane.org \
--cc=robdclark-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=rppt-tEXmvtCZX7AybS5Ee8rs3A@public.gmane.org \
--cc=will-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.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