From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dma-mapping: always clear allocated buffers
Date: Thu, 23 Apr 2015 15:28:17 +0100 [thread overview]
Message-ID: <20150423142816.GA16621@arm.com> (raw)
In-Reply-To: <1429789576-19570-1-git-send-email-m.szyprowski@samsung.com>
On Thu, Apr 23, 2015 at 12:46:16PM +0100, Marek Szyprowski wrote:
> Buffers allocated by dma_alloc_coherent() are always zeroed on Alpha,
> ARM (32bit), MIPS, PowerPC, x86/x86_64 and probably other architectures.
That's pretty compelling, even if it sucks. Maybe we could add a debug
option to poison DMA buffers if __GFP_ZERO isn't passed? It might help
others avoid the painful debugging experience you had...
Will
prev parent reply other threads:[~2015-04-23 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 11:46 [PATCH] arm64: dma-mapping: always clear allocated buffers Marek Szyprowski
2015-04-23 14:28 ` Will Deacon [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=20150423142816.GA16621@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).