From: Paul Cercueil <paul@crapouillou.net>
To: Christoph Hellwig <hch@lst.de>
Cc: Dave Airlie <airlied@linux.ie>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI <dri-devel@lists.freedesktop.org>
Subject: Re: linux-next: build failure after merge of the drm tree
Date: Wed, 30 Sep 2020 18:45:02 +0200 [thread overview]
Message-ID: <27DHHQ.SLESFBOY1GXP1@crapouillou.net> (raw)
In-Reply-To: <20200930164023.GA8645@lst.de>
Le mer. 30 sept. 2020 à 18:40, Christoph Hellwig <hch@lst.de> a écrit
:
> On Wed, Sep 30, 2020 at 06:39:18PM +0200, Paul Cercueil wrote:
>>> dma_alloc_pages gives you cached memory, so you can't just use an
>>> uncached protection for the userspace mmap here. If you want
>>> uncached
>>> memory you need to use dma_alloc_coherent paired with
>>> dma_mmap_coherent.
>>> Or dma_alloc_wc for a slightly different flavor of uncached. (both
>>> of the map to dma_alloc_attrs / dma_mmap_attrs eventually).
>>
>> I don't want uncached memory, I want non-coherent cached memory.
>
> We don't have such a thing in the Linux API at all.
dma_pgprot(dev, vma->vm_page_prot, DMA_ATTR_NON_CONSISTENT);
That was giving me non-coherent cached memory, and now I don't have an
alternative.
-Paul
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-10-01 8:16 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 3:54 linux-next: build failure after merge of the drm tree Stephen Rothwell
[not found] ` <20200928060427.GA15041@lst.de>
2020-09-28 6:08 ` Dave Airlie
2020-09-28 10:15 ` Paul Cercueil
[not found] ` <20200928113415.GA555@lst.de>
2020-09-28 11:46 ` Paul Cercueil
[not found] ` <20200928121002.GA3219@lst.de>
2020-09-28 13:31 ` Paul Cercueil
[not found] ` <20200930090252.GA9357@lst.de>
2020-09-30 13:33 ` Paul Cercueil
[not found] ` <20200930161124.GA6859@lst.de>
2020-09-30 16:39 ` Paul Cercueil
[not found] ` <20200930164023.GA8645@lst.de>
2020-09-30 16:45 ` Paul Cercueil [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-10 15:03 Mark Brown
2026-08-14 14:45 ` Mark Brown
2026-06-16 13:14 Mark Brown
2026-06-16 14:01 ` Vlastimil Babka (SUSE)
2026-06-16 14:12 ` Mark Brown
2026-06-03 13:32 Mark Brown
2026-03-10 15:25 Mark Brown
2026-03-10 15:36 ` Jacob Moroni
2026-03-10 15:42 ` Christian König
2026-02-10 21:08 Mark Brown
2025-12-04 4:24 Stephen Rothwell
2025-12-04 13:49 ` Alex Deucher
2025-04-28 3:30 Stephen Rothwell
2025-04-28 3:57 ` Dave Airlie
2025-04-28 4:24 ` Stephen Rothwell
2024-07-01 9:13 Stephen Rothwell
2024-07-01 17:19 ` Nathan Chancellor
2024-07-12 2:28 ` Stephen Rothwell
2024-07-12 3:12 ` David Airlie
2023-04-11 6:47 Stephen Rothwell
2023-01-19 2:12 Stephen Rothwell
[not found] <20220930105434.111407-1-broonie@kernel.org>
2022-10-04 2:20 ` Stephen Rothwell
2022-10-04 2:24 ` David Airlie
2022-10-04 3:05 ` Stephen Rothwell
2022-10-04 11:39 ` Mark Brown
2022-10-05 15:30 ` Alex Deucher
2022-10-05 16:45 ` Hamza Mahfooz
2022-10-05 22:28 ` Stephen Rothwell
2022-10-06 8:12 ` Stephen Rothwell
2022-10-06 13:56 ` Alex Deucher
2022-10-06 16:52 ` Stephen Rothwell
2022-10-06 16:25 ` Hamza Mahfooz
2022-02-25 16:42 broonie
2022-02-28 3:46 ` Stephen Rothwell
2022-02-28 6:44 ` Hsin-Yi Wang
2022-02-28 6:48 ` Dave Airlie
2022-02-28 15:33 ` Robert Foss
2022-03-01 6:58 ` Dave Airlie
2021-08-20 2:33 Stephen Rothwell
2021-08-20 6:23 ` Masahiro Yamada
2021-09-01 21:50 ` Stephen Rothwell
2021-09-05 22:49 ` Stephen Rothwell
2021-09-06 7:34 ` Daniel Vetter
2021-09-08 3:13 ` Masahiro Yamada
2021-09-08 9:07 ` Daniel Vetter
2021-04-09 3:36 Stephen Rothwell
2021-01-08 0:55 Stephen Rothwell
2021-01-08 1:25 ` Stephen Rothwell
2021-01-10 23:56 ` Stephen Rothwell
2021-01-18 0:59 ` Stephen Rothwell
2021-01-18 1:06 ` Dave Airlie
2021-01-20 12:12 ` Daniel Vetter
2021-01-20 20:44 ` Stephen Rothwell
2020-12-09 1:53 Stephen Rothwell
2020-05-08 4:29 Stephen Rothwell
2019-11-05 2:54 Stephen Rothwell
2019-11-05 2:54 ` Stephen Rothwell
2019-10-10 0:22 Stephen Rothwell
2019-07-08 4:48 Stephen Rothwell
2019-04-26 2:17 Stephen Rothwell
2018-05-16 6:53 Stephen Rothwell
2018-05-16 8:09 ` Oded Gabbay
2018-05-17 5:00 ` Dave Airlie
2018-03-13 5:46 Stephen Rothwell
2018-01-02 1:48 Stephen Rothwell
2017-03-20 0:51 Stephen Rothwell
2017-03-20 8:03 ` Daniel Vetter
2017-03-20 8:05 ` Daniel Vetter
2016-07-15 3:40 Stephen Rothwell
2016-07-15 4:32 ` Sedat Dilek
2016-04-28 1:57 Stephen Rothwell
2016-04-28 8:11 ` Jani Nikula
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=27DHHQ.SLESFBOY1GXP1@crapouillou.net \
--to=paul@crapouillou.net \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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