linux-kernel - Re: dma_declare_coherent

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: <20210628134955.GA22559@lst.de>
Date:   Mon, 28 Jun 2021 15:49:55 +0200
From:   Christoph Hellwig <hch@....de>
To:     Rob Landley <rob@...dley.net>
Cc:     Christoph Hellwig <hch@....de>,
        Yoshinori Sato <ysato@...rs.sourceforge.jp>,
        Rich Felker <dalias@...c.org>, linux-sh@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: dma_declare_coherent_memory and SuperH

On Mon, Jun 28, 2021 at 09:04:19AM -0500, Rob Landley wrote:
> > Well, the replacement is to declare the device memory carveouts in the
> > Device Tree.
> 
> Your plan is to eliminate the ability for non-device-tree boards to do DMA?

No.  My hope is to kill dma_declarare_coherent, an API for board
support files to declare device-specific regions to be used for
coherent DMA.