linux-kernel - Re: [PATCH 4/5] misc: vop: set VIRTIO_F_ACCESS

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: <20200926075123.GB18592@infradead.org>
Date:   Sat, 26 Sep 2020 08:51:23 +0100
From:   Christoph Hellwig <hch@...radead.org>
To:     Sherry Sun <sherry.sun@....com>
Cc:     sudeep.dutt@...el.com, ashutosh.dixit@...el.com, arnd@...db.de,
        gregkh@...uxfoundation.org, wang.yi59@....com.cn,
        huang.zijiang@....com.cn, rikard.falkeborn@...il.com,
        lee.jones@...aro.org, mst@...hat.com, linux-kernel@...r.kernel.org,
        linux-imx@....com
Subject: Re: [PATCH 4/5] misc: vop: set VIRTIO_F_ACCESS_PLATFORM for
 nocoherent platform

On Fri, Sep 25, 2020 at 03:26:29PM +0800, Sherry Sun wrote:
> Set VIRTIO_F_ACCESS_PLATFORM feature for nocoherent platform, since
> it needs the DMA API for virtio.

Given that VOP is a plug-in PCIe card VIRTIO_F_ACCESS_PLATFORM must
always be set, as the DMA mapping details are not something the
virtio implementation decides on, but the host PCIe/iommu
implementation.