virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: xuanzhuo@linux.alibaba.com, eperezma@redhat.com,
	virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
	hch@infradead.org
Subject: Re: [PATCH V6 0/9] Refine virtio mapping API
Date: Sun, 21 Sep 2025 18:15:39 -0400	[thread overview]
Message-ID: <20250921181435-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20250821064641.5025-1-jasowang@redhat.com>

On Thu, Aug 21, 2025 at 02:46:32PM +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 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.

I sent some typos i found.
Pls send fixups on top to fix them so testing in linux-next is not invalidated.
Thanks!



> Changes since V5:
> 
> - Rename mapping_token to virtio_map
> - Do not use opaque void * pointer, just use a forward decalration of
>   vduse_iova_domain
> - Remove unused variable and typo fixes
> 
> Changes since V4:
> 
> - Rename map_token to mapping_token
> - Introduce a union container for opaque token as well as the DMA
>   device so we won't lose the type safety
> - Do not try to set DMA mask for VDUSE device
> - Introduce a new mapper_error op for API completeness
> 
> 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: introduce virtio_map container union
>   virtio_ring: rename dma_handle to map_handle
>   virtio: introduce map ops in virtio core
>   vdpa: support virtio_map
>   vdpa: introduce map ops
>   vduse: switch to use virtio map API instead of DMA API
> 
>  drivers/net/virtio_net.c                 |  28 +-
>  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        |  15 +-
>  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     |   2 +-
>  drivers/vdpa/vdpa_user/iova_domain.h     |   2 +-
>  drivers/vdpa/vdpa_user/vduse_dev.c       |  79 ++--
>  drivers/vdpa/virtio_pci/vp_vdpa.c        |   5 +-
>  drivers/vhost/vdpa.c                     |   6 +-
>  drivers/virtio/virtio_ring.c             | 459 ++++++++++++++---------
>  drivers/virtio/virtio_vdpa.c             |  20 +-
>  include/linux/vdpa.h                     |  25 +-
>  include/linux/virtio.h                   |  46 ++-
>  include/linux/virtio_config.h            |  72 ++++
>  include/linux/virtio_ring.h              |   7 +-
>  22 files changed, 531 insertions(+), 285 deletions(-)
> 
> -- 
> 2.31.1


  parent reply	other threads:[~2025-09-21 22:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21  6:46 [PATCH V6 0/9] Refine virtio mapping API Jason Wang
2025-08-21  6:46 ` [PATCH V6 1/9] virtio_ring: constify virtqueue pointer for DMA helpers Jason Wang
2025-08-21  6:46 ` [PATCH V6 2/9] virtio_ring: switch to use dma_{map|unmap}_page() Jason Wang
2025-08-21  6:46 ` [PATCH V6 3/9] virtio: rename dma helpers Jason Wang
2025-09-21 22:13   ` Michael S. Tsirkin
2025-08-21  6:46 ` [PATCH V6 4/9] virtio: introduce virtio_map container union Jason Wang
2025-08-21  6:46 ` [PATCH V6 5/9] virtio_ring: rename dma_handle to map_handle Jason Wang
2025-08-21  6:46 ` [PATCH V6 6/9] virtio: introduce map ops in virtio core Jason Wang
2025-09-21 22:01   ` Michael S. Tsirkin
2025-09-21 22:03   ` Michael S. Tsirkin
2025-09-21 22:06   ` Michael S. Tsirkin
2025-08-21  6:46 ` [PATCH V6 7/9] vdpa: support virtio_map Jason Wang
2025-08-21  6:46 ` [PATCH V6 8/9] vdpa: introduce map ops Jason Wang
2025-09-21 21:52   ` Michael S. Tsirkin
2025-09-21 21:58   ` Michael S. Tsirkin
2025-08-21  6:46 ` [PATCH V6 9/9] vduse: switch to use virtio map API instead of DMA API Jason Wang
2025-08-25  3:18 ` [PATCH V6 0/9] Refine virtio mapping API Lei Yang
2025-08-26 11:30 ` Eugenio Perez Martin
2025-09-21 22:15 ` Michael S. Tsirkin [this message]
2025-09-22  1:06   ` 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=20250921181435-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=eperezma@redhat.com \
    --cc=hch@infradead.org \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).