From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Shawn Anastasio <shawn@anastas.io>, linuxppc-dev@lists.ozlabs.org
Cc: aik@ozlabs.ru, sbobroff@linux.ibm.com
Subject: Re: [PATCH] powerpc/dma: Fix invalid DMA mmap behavior
Date: Mon, 22 Jul 2019 12:48:15 +1000 (AEST) [thread overview]
Message-ID: <45sQyl0Vglz9sBZ@ozlabs.org> (raw)
In-Reply-To: <20190717235437.12908-1-shawn@anastas.io>
On Wed, 2019-07-17 at 23:54:37 UTC, Shawn Anastasio wrote:
> The refactor of powerpc DMA functions in commit 6666cc17d780
> ("powerpc/dma: remove dma_nommu_mmap_coherent") incorrectly
> changes the way DMA mappings are handled on powerpc.
> Since this change, all mapped pages are marked as cache-inhibited
> through the default implementation of arch_dma_mmap_pgprot.
> This differs from the previous behavior of only marking pages
> in noncoherent mappings as cache-inhibited and has resulted in
> sporadic system crashes in certain hardware configurations and
> workloads (see Bugzilla).
>
> This commit restores the previous correct behavior by providing
> an implementation of arch_dma_mmap_pgprot that only marks
> pages in noncoherent mappings as cache-inhibited. As this behavior
> should be universal for all powerpc platforms a new file,
> dma-generic.c, was created to store it.
>
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=204145
> Fixes: 6666cc17d780 ("powerpc/dma: remove dma_nommu_mmap_coherent")
> Signed-off-by: Shawn Anastasio <shawn@anastas.io>
> Reviewed-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/b4fc36e60f25cf22bf8b7b015a701015740c3743
cheers
prev parent reply other threads:[~2019-07-22 2:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 23:54 [PATCH] powerpc/dma: Fix invalid DMA mmap behavior Shawn Anastasio
2019-07-18 2:59 ` Alexey Kardashevskiy
2019-07-18 3:14 ` Shawn Anastasio
2019-07-18 3:45 ` Oliver O'Halloran
2019-07-18 8:49 ` Christoph Hellwig
2019-07-18 9:52 ` Christoph Hellwig
2019-07-18 19:46 ` Shawn Anastasio
2019-07-19 7:06 ` Christoph Hellwig
2019-07-19 7:36 ` Shawn Anastasio
2019-07-19 11:18 ` Arnd Bergmann
2019-07-22 12:16 ` Michael Ellerman
2019-07-22 19:23 ` Shawn Anastasio
2019-07-22 23:09 ` Michael Ellerman
2019-07-22 2:48 ` Michael Ellerman [this message]
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=45sQyl0Vglz9sBZ@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=aik@ozlabs.ru \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sbobroff@linux.ibm.com \
--cc=shawn@anastas.io \
/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).