linux-kernel - Re: use the generic dma-noncoherent code for openrisc

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: <20180721053142.GC9742@lianli.shorne-pla.net>
Date:   Sat, 21 Jul 2018 14:31:42 +0900
From:   Stafford Horne <shorne@...il.com>
To:     Christoph Hellwig <hch@....de>
Cc:     Jonas Bonn <jonas@...thpole.se>,
        Stefan Kristiansson <stefan.kristiansson@...nalahti.fi>,
        openrisc@...ts.librecores.org, iommu@...ts.linux-foundation.org,
        linux-kernel@...r.kernel.org
Subject: Re: use the generic dma-noncoherent code for openrisc

On Thu, Jul 19, 2018 at 06:02:28AM -0700, Christoph Hellwig wrote:
> Hi Openrisc maintainers,
> 
> can you review these patches to switch openrisc to use the generic
> dma-noncoherent code?  All the requirements are in mainline already
> and we've switched various architectures over to it already.

Hi Christoph,

Thanks for this, these look good to me.  I don't know much about the dma
infrastructure in the kernel to tell the truth, but the patches do maintain the
original cache flushing and invalidation core logic and I don't see any
problems.

I have applied these and ran my regular tests, but I don't really have any DMA
hardware so the testing doesn't mean much.

For upstreaming, do you want me to send these through the openrisc tree, or do
you want to send with the dma tree?

-Stafford