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, hch@infradead.org
Subject: Re: [PATCH V3 0/9] Refine virtio mapping API
Date: Fri, 18 Jul 2025 04:49:13 -0400 [thread overview]
Message-ID: <20250718044839-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CACGkMEsPPxVB5mgcT4=6xL5trBHn33_P1pqxgti-4FSqdYZ5vQ@mail.gmail.com>
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@redhat.com> 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?
next prev parent reply other threads:[~2025-07-18 8:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 2:37 [PATCH V3 0/9] Refine virtio mapping API Jason Wang
2025-07-18 2:37 ` [PATCH V3 1/9] virtio_ring: constify virtqueue pointer for DMA helpers Jason Wang
2025-07-18 8:46 ` Michael S. Tsirkin
2025-07-18 2:37 ` [PATCH V3 2/9] virtio_ring: switch to use dma_{map|unmap}_page() Jason Wang
2025-07-18 2:37 ` [PATCH V3 3/9] virtio: rename dma helpers Jason Wang
2025-07-18 2:37 ` [PATCH V3 4/9] virtio: rename dma_dev to map_token Jason Wang
2025-07-18 2:37 ` [PATCH V3 5/9] virtio_ring: rename dma_handle to map_handle Jason Wang
2025-07-18 2:37 ` [PATCH V3 6/9] virtio: introduce map ops in virtio core Jason Wang
2025-07-18 2:37 ` [PATCH V3 7/9] vdpa: rename dma_dev to map_token Jason Wang
2025-07-18 2:37 ` [PATCH V3 8/9] vdpa: introduce map ops Jason Wang
2025-07-18 2:37 ` [PATCH V3 9/9] vduse: switch to use virtio map API instead of DMA API Jason Wang
2025-07-18 4:23 ` [PATCH V3 0/9] Refine virtio mapping API Jason Wang
2025-07-18 8:49 ` Michael S. Tsirkin [this message]
2025-07-18 8:53 ` Jason Wang
2025-07-18 8:54 ` 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=20250718044839-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eperezma@redhat.com \
--cc=hch@infradead.org \
--cc=jasowang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.