linux-kernel - Re: [RFC LINUX PATCH 0/3] Allow remote to specify shared memory

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]

Message-ID: <df420852-6b5a-a2fc-4c4c-8556b9985e29@ti.com>
Date:   Mon, 27 Mar 2017 10:54:44 -0500
From:   Suman Anna <s-anna@...com>
To:     Wendy Liang <wendy.liang@...inx.com>, <bjorn.andersson@...aro.org>
CC:     <linux-remoteproc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        Wendy Liang <jliang@...inx.com>
Subject: Re: [RFC LINUX PATCH 0/3] Allow remote to specify shared memory

Hi Wendy,

On 03/24/2017 02:22 PM, Wendy Liang wrote:
> This patch enables the remoteproc to specify the shared memory.
> Remoteproc declared this memory as DMA memory.
> It can be used for virtio, or shared buffers.

You should be able to achieve this without any remoteproc core changes.
You can do this by defining a reserved-memory node in your DTS file (can
be a CMA pool or a DMA pool), assigning the node using memory-region in
your remoteproc DT node and using the function,
of_reserved_mem_device_init() in your remoteproc driver.

regards
Suman

> 
> Wendy Liang (3):
>   remoteproc: add rproc mem resource entry
>   remoteproc: add rproc_mem resource entry handler
>   remoteproc: Release DMA declare mem when cleanup rsc
> 
>  drivers/remoteproc/remoteproc_core.c | 40 ++++++++++++++++++++++++++++++++++++
>  include/linux/remoteproc.h           | 23 ++++++++++++++++++++-
>  2 files changed, 62 insertions(+), 1 deletion(-)
>