On Fri, Jul 18, 2025 at 4:53 PM Jason Wang <jasowang@xxxxxxxxxx> wrote: > > On Fri, Jul 18, 2025 at 4:49 PM Michael S. Tsirkin <mst@xxxxxxxxxx> wrote: > > > > On Fri, Jul 18, 2025 at 12:23:49PM +0800, Jason Wang wrote: > > > On Fri, Jul 18, 2025 at 10:38 AM Jason Wang <jasowang@xxxxxxxxxx> 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 tries to solve this issue by introducing the mapping API > > > > in the virtio core. So transport like vDPA can implement their own > > > > mapping logic without the need to hack with DMA API. The mapping API > > > > are abstracted with a new map operations in order to be re-used by > > > > transprot or device. So device like VDUSE can implement its own > > > > mapping loigc. > > > > > > > > For device that uses DMA (for example PCI device), the virtio core > > > > will still call DMA API directly without the need of implementing map > > > > ops per device/transport. > > > > > > > > Please review. > > > > > > > > Changes since V2: > > > > > > > > - Drop VDUSE dependenct for HAS_DMA and ARCH_HAS_DMA_OPS > > > > > > I just realized V2 has been merged. So I will post an independent > > > patch to do this on top. > > > > > > Thanks > > > > Dropped for now. Posted a comment though. does v3 fix the build failure > > in linux-next? > > > > I didn't find the report, maybe you can give me a pointer? > > Thanks Just saw that. Let me fix it. Thanks
