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

2025-07-03 Thread Christoph Hellwig
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

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

2025-07-01 Thread Jason Wang
On Tue, Jul 1, 2025 at 3:04 PM Michael S. Tsirkin wrote: > > On Tue, Jul 01, 2025 at 09:13:52AM +0800, Jason Wang wrote: > > Hi all: > > > > Virtio used to be coupled with DMA API. This works fine for the device > > that do real DMA but not the others. For example, VDUSE nees to craft > > with DMA

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

2025-07-01 Thread Michael S. Tsirkin
On Tue, Jul 01, 2025 at 09:13:52AM +0800, Jason Wang wrote: > Hi all: > > Virtio used to be coupled with DMA API. This works fine for the device > that do real DMA but not the others. For example, VDUSE nees to craft > with DMA API in order to let the virtio-vdpa driver to work. > > This series t

[PATCH 0/9] Refine virtio mapping API

2025-06-30 Thread Jason Wang
Hi all: Virtio used to be coupled with DMA API. This works fine for the device that do real DMA but not the others. For example, VDUSE nees to craft with DMA API in order to let the virtio-vdpa driver to work. This series tries to solve this issue by introducing the mapping API in the virtio core