From: Vladimir Murzin <vladimir.murzin@arm.com>
To: Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
kbuild-all@01.org, linux@armlinux.org.uk, jroedel@suse.de,
borntraeger@de.ibm.com, mina86@mina86.com,
m.szyprowski@samsung.com, stern@rowland.harvard.edu,
ysato@users.sourceforge.jp, dalias@libc.org, rogerq@ti.com,
gregkh@linuxfoundation.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH 0/7] ARM: Fix dma_alloc_coherent() and friends for NOMMU
Date: Tue, 21 Feb 2017 12:27:45 +0000 [thread overview]
Message-ID: <a0ec7767-c3d1-20b7-48c5-ef71be5918e1@arm.com> (raw)
In-Reply-To: <c713deed-b2bd-e413-70e2-08c51c1f8c3e@arm.com>
Hi Robin,
On 21/02/17 12:16, Robin Murphy wrote:
> Hi Vladimir,
>
> On 21/02/17 10:41, Vladimir Murzin wrote:
>> Gentle ping!
>
> What's your plan for this series? Are you looking for acks on the common
> parts to take it through the ARM tree, or Russell's ack on the ARM parts
> for it to go through mm?
Nothing particular in my mind - either way would work me. So far I have not
heard feedback on common parts and it is not clear to me who should give Ack
on them :(
>
> Either way, I expect the merge window is probably consuming most folks'
> attention just now.
I see.
Cheers
Vladimir
>
> Robin.
>
>> Cc: Joerg Roedel <jroedel@suse.de>
>> Cc: Christian Borntraeger <borntraeger@de.ibm.com>
>> Cc: Michal Nazarewicz <mina86@mina86.com>
>> Cc: Marek Szyprowski <m.szyprowski@samsung.com>
>> Cc: Alan Stern <stern@rowland.harvard.edu>
>> Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
>> Cc: Rich Felker <dalias@libc.org>
>> Cc: Roger Quadros <rogerq@ti.com>
>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> Cc: Rob Herring <robh+dt@kernel.org>
>> Cc: Mark Rutland <mark.rutland@arm.com>
>>
>> On 15/02/17 09:59, Vladimir Murzin wrote:
>>> Hi,
>>>
>>> It seem that addition of cache support for M-class CPUs uncovered
>>> latent bug in DMA usage. NOMMU memory model has been treated as being
>>> always consistent; however, for R/M CPU classes memory can be covered
>>> by MPU which in turn might configure RAM as Normal i.e. bufferable and
>>> cacheable. It breaks dma_alloc_coherent() and friends, since data can
>>> stuck in caches now or be buffered.
>>>
>>> This patch set is trying to address the issue by providing region of
>>> memory suitable for consistent DMA operations. It is supposed that
>>> such region is marked by MPU as non-cacheable. Robin suggested to
>>> advertise such memory as reserved shared-dma-pool, rather then using
>>> homebrew command line option, and extend dma-coherent to provide
>>> default DMA area in the similar way as it is done for CMA (PATCH
>>> 4/7). It allows us to offload all bookkeeping on generic coherent DMA
>>> framework, and it seems that it might be reused by other architectures
>>> like c6x and blackfin.
>>>
>>> While reviewing/testing previous vesrions of the patch set it turned
>>> out that dma-coherent does not take into account "dma-ranges" device
>>> tree property, so it is addressed in PATCH 3/7.
>>>
>>> For ARM, dedicated DMA region is required for cases other than:
>>> - MMU/MPU is off
>>> - cpu is v7m w/o cache support
>>> - device is coherent
>>>
>>> In case one of the above conditions is true dma operations are forced
>>> to be coherent and wired with dma_noop_ops.
>>>
>>> To make life easier NOMMU dma operations are kept in separate
>>> compilation unit.
>>>
>>> Since the issue was reported in the same time as Benjamin sent his
>>> patch [1] to allow mmap for NOMMU, his case is also addressed in this
>>> series (PATCH 1/7 and PATCH 2/7).
>>>
>>> Thanks!
>>>
>>> [1] http://www.armlinux.org.uk/developer/patches/viewpatch.php?id=8633/1
>>>
>>> Changelog:
>>> RFC v6 -> v1
>>> - dropped RFC tag
>>> - added Alexandre's Tested-by
>>>
>>> Vladimir Murzin (7):
>>> dma: Take into account dma_pfn_offset
>>> dma: Add simple dma_noop_mmap
>>> drivers: dma-coherent: Account dma_pfn_offset when used with device
>>> tree
>>> drivers: dma-coherent: Introduce default DMA pool
>>> ARM: NOMMU: Introduce dma operations for noMMU
>>> ARM: NOMMU: Set ARM_DMA_MEM_BUFFERABLE for M-class cpus
>>> ARM: dma-mapping: Remove traces of NOMMU code
>>>
>>> .../bindings/reserved-memory/reserved-memory.txt | 3 +
>>> arch/arm/include/asm/dma-mapping.h | 3 +-
>>> arch/arm/mm/Kconfig | 2 +-
>>> arch/arm/mm/Makefile | 5 +-
>>> arch/arm/mm/dma-mapping-nommu.c | 253 +++++++++++++++++++++
>>> arch/arm/mm/dma-mapping.c | 26 +--
>>> drivers/base/dma-coherent.c | 76 ++++++-
>>> lib/dma-noop.c | 29 ++-
>>> 8 files changed, 356 insertions(+), 41 deletions(-)
>>> create mode 100644 arch/arm/mm/dma-mapping-nommu.c
>>>
>>
>
>
prev parent reply other threads:[~2017-02-21 12:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 9:59 Vladimir Murzin
2017-02-15 9:59 ` [PATCH 1/7] dma: Take into account dma_pfn_offset Vladimir Murzin
2017-02-21 13:07 ` Robin Murphy
2017-02-21 13:20 ` Vladimir Murzin
2017-02-15 9:59 ` [PATCH 2/7] dma: Add simple dma_noop_mmap Vladimir Murzin
2017-02-15 9:59 ` [PATCH 3/7] drivers: dma-coherent: Account dma_pfn_offset when used with device tree Vladimir Murzin
2017-02-21 12:37 ` Robin Murphy
2017-02-21 13:02 ` Vladimir Murzin
2017-02-21 13:05 ` Vladimir Murzin
2017-02-21 17:11 ` Robin Murphy
2017-02-15 9:59 ` [PATCH 4/7] drivers: dma-coherent: Introduce default DMA pool Vladimir Murzin
2017-02-15 9:59 ` [PATCH 5/7] ARM: NOMMU: Introduce dma operations for noMMU Vladimir Murzin
2017-02-15 9:59 ` [PATCH 6/7] ARM: NOMMU: Set ARM_DMA_MEM_BUFFERABLE for M-class cpus Vladimir Murzin
2017-02-21 12:57 ` Robin Murphy
2017-02-21 13:03 ` Vladimir Murzin
2017-02-15 9:59 ` [PATCH 7/7] ARM: dma-mapping: Remove traces of NOMMU code Vladimir Murzin
2017-02-21 10:41 ` [PATCH 0/7] ARM: Fix dma_alloc_coherent() and friends for NOMMU Vladimir Murzin
2017-02-21 12:16 ` Robin Murphy
2017-02-21 12:27 ` Vladimir Murzin [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=a0ec7767-c3d1-20b7-48c5-ef71be5918e1@arm.com \
--to=vladimir.murzin@arm.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=dalias@libc.org \
--cc=gregkh@linuxfoundation.org \
--cc=jroedel@suse.de \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=mark.rutland@arm.com \
--cc=mina86@mina86.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rogerq@ti.com \
--cc=stern@rowland.harvard.edu \
--cc=ysato@users.sourceforge.jp \
/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
all inboxes | Powered by JetHome®