linux-kernel - Re: [PATCH 1/2] drivers: dma-coherent: Add support for default DMA coherent pool

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 9 Jul 2017 19:36:08 -0500
From:   Rob Herring <robh@...nel.org>
To:     vitaly_kuzmichev@...tor.com
Cc:     gregkh@...uxfoundation.org, mark.rutland@....com,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
        george_davis@...tor.com
Subject: Re: [PATCH 1/2] drivers: dma-coherent: Add support for default DMA
 coherent pool

On Mon, Jul 03, 2017 at 05:51:14PM +0300, vitaly_kuzmichev@...tor.com wrote:
> From: "George G. Davis" <george_davis@...tor.com>
> 
> Use concept similar to the default CMA region for DMA coherent pools.

Why do we need this in DT? CMA is a carveout and has to be reserved 
early, but DMA coherent memory is just different MMU attributes, right?

Also, does this still apply with DMA mapping changes in 4.13?

> Cc: Rob Herring <robh+dt@...nel.org>
> Cc: Mark Rutland <mark.rutland@....com>
> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Signed-off-by: George G. Davis <george_davis@...tor.com>
> Signed-off-by: Jiada Wang <jiada_wang@...tor.com>
> Signed-off-by: Mark Craske <Mark_Craske@...tor.com>
> Signed-off-by: Vitaly Kuzmichev <Vitaly_Kuzmichev@...tor.com>
> ---
>  .../bindings/reserved-memory/reserved-memory.txt   |  2 ++
>  drivers/base/dma-coherent.c                        | 29 ++++++++++++++++------
>  2 files changed, 24 insertions(+), 7 deletions(-)