From: vladimir.murzin@arm.com (Vladimir Murzin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/7] ARM: Fix dma_alloc_coherent() and friends for NOMMU
Date: Wed, 29 Mar 2017 09:17:14 +0100 [thread overview]
Message-ID: <4e3ce329-6194-043b-0d69-cbec6b08e38e@arm.com> (raw)
In-Reply-To: <186f0c06-39ce-cb88-35e5-6dd57aa81166@arm.com>
Ping!
On 23/03/17 09:26, Vladimir Murzin wrote:
> On 22/03/17 12:23, Szemz? Andr?s wrote:
>> I?ve tested this v3 version on my Atmel armv7m board with several drivers with DMA and enabled caches,
>> and I?ve not seen any issues.
>>
>> You can add my Tested-by.
>
> Much appreciated!
>
> Russell, Andrew, Greg, any advise on how to get this series merged? Patches
> has been circulated on a list since December last year and without them Andr?s
> and Alexandre cannot safely enable DMA on their platforms.
>
> Cheers
> Vladimir
>
>>
>> Thanks for the patches!
>>
>> Andras
>>
>>> On 2017. Mar 16., at 10:03, Vladimir Murzin <vladimir.murzin@arm.com> wrote:
>>>
>>> Gentle ping!
>>>
>>> On 10/03/17 09:23, Vladimir Murzin wrote:
>>>> 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
>>>>
>>>> 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>
>>>> Cc: Doug Ledford <dledford@redhat.com>
>>>>
>>>> Changelog:
>>>> v2 -> v3
>>>> - fixed warnings reported by Alexandre and kbuild robot
>>>>
>>>> v1 -> v2
>>>> - rebased on v4.11-rc1
>>>> - added Robin's Reviewed-by
>>>> - dedicated flag is introduced to use dev->dma_pfn_offset
>>>> rather than mem->device_base in case memory region is
>>>> configured via device tree (so Tested-by discarded there)
>>>>
>>>> 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/Kconfig | 1 +
>>>> arch/arm/include/asm/dma-mapping.h | 2 +-
>>>> arch/arm/mm/Kconfig | 2 +-
>>>> arch/arm/mm/Makefile | 5 +-
>>>> arch/arm/mm/dma-mapping-nommu.c | 253 +++++++++++++++++++++
>>>> arch/arm/mm/dma-mapping.c | 29 +--
>>>> drivers/base/dma-coherent.c | 74 +++++-
>>>> lib/dma-noop.c | 29 ++-
>>>> 9 files changed, 354 insertions(+), 44 deletions(-)
>>>> create mode 100644 arch/arm/mm/dma-mapping-nommu.c
>>>>
>>>
>>
>>
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2017-03-29 8:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 9:23 [PATCH v3 0/7] ARM: Fix dma_alloc_coherent() and friends for NOMMU Vladimir Murzin
2017-03-10 9:23 ` [PATCH v3 1/7] dma: Take into account dma_pfn_offset Vladimir Murzin
2017-03-10 9:23 ` [PATCH v3 2/7] dma: Add simple dma_noop_mmap Vladimir Murzin
2017-03-10 9:23 ` [PATCH v3 3/7] drivers: dma-coherent: Account dma_pfn_offset when used with device tree Vladimir Murzin
2017-03-10 9:23 ` [PATCH v3 4/7] drivers: dma-coherent: Introduce default DMA pool Vladimir Murzin
2017-03-10 9:23 ` [PATCH v3 5/7] ARM: NOMMU: Introduce dma operations for noMMU Vladimir Murzin
2017-04-19 10:10 ` Arnd Bergmann
2017-04-19 14:12 ` Vladimir Murzin
2017-03-10 9:23 ` [PATCH v3 6/7] ARM: NOMMU: Set ARM_DMA_MEM_BUFFERABLE for M-class cpus Vladimir Murzin
2017-04-19 10:02 ` Arnd Bergmann
2017-04-19 14:10 ` Vladimir Murzin
2017-04-21 22:12 ` Arnd Bergmann
2017-03-10 9:23 ` [PATCH v3 7/7] ARM: dma-mapping: Remove traces of NOMMU code Vladimir Murzin
2017-04-19 9:56 ` Arnd Bergmann
2017-04-19 14:11 ` Vladimir Murzin
2017-03-16 9:03 ` [PATCH v3 0/7] ARM: Fix dma_alloc_coherent() and friends for NOMMU Vladimir Murzin
2017-03-22 12:23 ` Szemző András
2017-03-23 9:26 ` Vladimir Murzin
2017-03-29 8:17 ` Vladimir Murzin [this message]
2017-04-18 12:51 ` Vladimir Murzin
2017-04-19 11:56 ` Joerg Roedel
2017-04-19 14:20 ` Vladimir Murzin
2017-05-11 14:44 ` Benjamin Gaignard
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=4e3ce329-6194-043b-0d69-cbec6b08e38e@arm.com \
--to=vladimir.murzin@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).