From: Jason Wang <jasowang@redhat.com>
To: mst@redhat.com, jasowang@redhat.com, xuanzhuo@linux.alibaba.com,
eperezma@redhat.com
Cc: virtualization@lists.linux.dev, hch@infradead.org
Subject: [PATCH V4 0/9] Refine virtio mapping API
Date: Fri, 18 Jul 2025 17:15:44 +0800 [thread overview]
Message-ID: <20250718091553.6108-1-jasowang@redhat.com> (raw)
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 V3:
- Fix build error of PDS vDPA driver
Changes since V2:
- Drop VDUSE dependenct for HAS_DMA and ARCH_HAS_DMA_OPS
Changes since V1:
- Fix build error of mlx5_vdpa driver
Jason Wang (9):
virtio_ring: constify virtqueue pointer for DMA helpers
virtio_ring: switch to use dma_{map|unmap}_page()
virtio: rename dma helpers
virtio: rename dma_dev to map_token
virtio_ring: rename dma_handle to map_handle
virtio: introduce map ops in virtio core
vdpa: rename dma_dev to map_token
vdpa: introduce map ops
vduse: switch to use virtio map API instead of DMA API
drivers/net/virtio_net.c | 32 +-
drivers/vdpa/Kconfig | 8 +-
drivers/vdpa/alibaba/eni_vdpa.c | 5 +-
drivers/vdpa/ifcvf/ifcvf_main.c | 5 +-
drivers/vdpa/mlx5/core/mr.c | 4 +-
drivers/vdpa/mlx5/net/mlx5_vnet.c | 10 +-
drivers/vdpa/octeon_ep/octep_vdpa_main.c | 6 +-
drivers/vdpa/pds/vdpa_dev.c | 5 +-
drivers/vdpa/solidrun/snet_main.c | 8 +-
drivers/vdpa/vdpa.c | 5 +-
drivers/vdpa/vdpa_sim/vdpa_sim.c | 4 +-
drivers/vdpa/vdpa_user/iova_domain.c | 8 +-
drivers/vdpa/vdpa_user/iova_domain.h | 5 +-
drivers/vdpa/vdpa_user/vduse_dev.c | 34 +-
drivers/vdpa/virtio_pci/vp_vdpa.c | 5 +-
drivers/vhost/vdpa.c | 11 +-
drivers/virtio/virtio_ring.c | 440 ++++++++++++++---------
drivers/virtio/virtio_vdpa.c | 15 +-
include/linux/vdpa.h | 22 +-
include/linux/virtio.h | 36 +-
include/linux/virtio_config.h | 68 ++++
include/linux/virtio_ring.h | 6 +-
22 files changed, 487 insertions(+), 255 deletions(-)
--
2.47.3
next reply other threads:[~2025-07-18 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 9:15 Jason Wang [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-18 9:16 [PATCH V4 0/9] Refine virtio mapping API Jason Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250718091553.6108-1-jasowang@redhat.com \
--to=jasowang@redhat.com \
--cc=eperezma@redhat.com \
--cc=hch@infradead.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox