linux-kernel - Re: [PATCH 10/11] soc: ti: k3-ringacc: Use correct device for allocation in RING mode

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: <3bbe1568-3ceb-07df-4c40-bcc54c8935c0@ti.com>
Date:   Wed, 30 Sep 2020 16:58:14 +0300
From:   Grygorii Strashko <grygorii.strashko@...com>
To:     Peter Ujfalusi <peter.ujfalusi@...com>, <nm@...com>,
        <t-kristo@...com>, <ssantosh@...nel.org>, <lokeshvutla@...com>
CC:     <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 10/11] soc: ti: k3-ringacc: Use correct device for
 allocation in RING mode



On 28/09/2020 11:34, Peter Ujfalusi wrote:
> In RING mode the ringacc does not access the ring memory. In this access
> mode the ringacc coherency does not have meaning.
> 
> If the ring is configured in RING mode, then the ringacc itself will not
> access to the ring memory. Only the requester (user) of the ring is going
> to read/write to the memory.
> Extend the ring configuration parameters with a device pointer to be used
> for DMA API when the ring is configured in RING mode.
> 
> Extending the ring configuration struct will allow per ring selection of
> device to be used for allocation, thus allowing per ring coherency.
> 
> To avoid regression, fall back to use the ringacc dev in case the alloc_dev
> is not provided.
> 
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@...com>
> ---
>   drivers/soc/ti/k3-ringacc.c       | 14 +++++++++++---
>   include/linux/soc/ti/k3-ringacc.h |  5 +++++
>   2 files changed, 16 insertions(+), 3 deletions(-)
> 
Reviewed-by: Grygorii Strashko <grygorii.strashko@...com>

-- 
Best regards,
grygorii