linux-kernel - Re: [PATCH 0/9] Refine virtio mapping API

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] [day] [month] [year] [list]

Message-ID: <aGZF4025JPO3wgnm@infradead.org>
Date: Thu, 3 Jul 2025 01:57:07 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Jason Wang <jasowang@...hat.com>
Cc: "Michael S. Tsirkin" <mst@...hat.com>, xuanzhuo@...ux.alibaba.com,
	eperezma@...hat.com, virtualization@...ts.linux.dev,
	linux-kernel@...r.kernel.org, hch@...radead.org,
	xieyongji@...edance.com
Subject: Re: [PATCH 0/9] Refine virtio mapping API

On Tue, Jul 01, 2025 at 04:00:31PM +0800, Jason Wang wrote:
> Actually not, it doesn't change how things work for the device that
> does DMA already like:
> 
> If device has its specific mapping ops
>         go for device specific mapping ops
> else
>         go for DMA API
> 
> VDUSE is the only user now, and extra indirection has been used for
> VDUSE even without this series (via abusing DMA API). This series
> switch from:
> 
> virtio core -> DMA API -> VDUSE DMA API -> iova domain ops
> 
> to
> 
> virtio core -> virtio map ops -> VDUSE map ops -> iova domain ops

And that's exaxctly how it should be done.

Thanks for doing the work!  I'll go through if I find some nitpicks,
but the concept is the only right one here.