From: Jason Wang <jasowang@redhat.com>
To: Wafer <wafer@jaguarmicro.com>
Cc: "mst@redhat.com" <mst@redhat.com>,
"eperezma@redhat.com" <eperezma@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"leiyang@redhat.com" <leiyang@redhat.com>,
"sgarzare@redhat.com" <sgarzare@redhat.com>,
Angus Chen <angus.chen@jaguarmicro.com>
Subject: Re: [PATCH 0/4] Add Split indirect descriptors for SVQ
Date: Fri, 5 Dec 2025 09:33:02 +0800 [thread overview]
Message-ID: <CACGkMEvchy+JeF29VuoHHuK2XVfKdXT1_Z-HP6TS7fr8DkSusw@mail.gmail.com> (raw)
In-Reply-To: <PUZPR06MB471395120934B469F9315B12A2A7A@PUZPR06MB4713.apcprd06.prod.outlook.com>
On Fri, Dec 5, 2025 at 9:30 AM Wafer <wafer@jaguarmicro.com> wrote:
>
>
>
> > -----Original Message-----
> > From: Jason Wang <jasowang@redhat.com>
> > Sent: 2025年12月4日 15:56
> > To: Wafer <wafer@jaguarmicro.com>
> > Cc: mst@redhat.com; eperezma@redhat.com; qemu-devel@nongnu.org;
> > leiyang@redhat.com; sgarzare@redhat.com; Angus Chen
> > <angus.chen@jaguarmicro.com>
> > Subject: Re: [PATCH 0/4] Add Split indirect descriptors for SVQ
> >
> > External Mail: This email originated from OUTSIDE of the organization!
> > Do not click links, open attachments or provide ANY information unless you
> > recognize the sender and know the content is safe.
> >
> >
> > On Thu, Dec 4, 2025 at 3:38 PM Wafer Xie <wafer@jaguarmicro.com> wrote:
> > >
> > > This patch series adds support for VIRTIO split indirect descriptors.
> > > The feature is VIRTIO_RING_F_INDIRECT_DESC.
> > >
> > > Eugenio hs submitted a patch: vhost: accept indirect descriptors in
> > > shadow virtqueue
> > > https://lists.nongnu.org/archive/html/qemu-devel/2025-
> > 12/msg00056.html
> > > Therefore, this patch must be applied first.
> >
> > I may miss something but svq can read indirect descriptors even though it
> > doesn't use indirect descriptor, that's sufficient for making it claims to
> > support indirect descriptors. That's what Eugenio said in that series.
> >
> > This series could be an optimization on top?
> >
> > Thanks
> >
>
> Thanks for your reply!
> Right, the current svq implementation can read the indirect descriptors provided by the driver, but it cannot use indirect descriptors when interacting with the backend device.
> However, if a backend device implements indirect descriptors and wants to use QEMU to validate its indirect descriptor support, then QEMU needs to fully support indirect descriptors in this path. This series is intended to provide that full support, so that such backend devices can be properly tested and validated via QEMU.
Great, let's tweak the changelog for the next version like this.
Thanks
>
> > >
> > >
> > > Wafer Xie (4):
> > > vhost: add data structure of virtio indirect descriptors in SVQ
> > > vdpa: implement the interfaces alloc/free for indirect desc
> > > vhost: supported the virtio indirect desc of available ring
> > > vhost: supported the viriot indriect desc of used ring
> > >
> > > hw/virtio/vhost-shadow-virtqueue.c | 224
> > > +++++++++++++++++++++++++++-- hw/virtio/vhost-shadow-virtqueue.h
> > | 57 +++++++-
> > > hw/virtio/vhost-vdpa.c | 130 ++++++++++++++++-
> > > 3 files changed, 395 insertions(+), 16 deletions(-)
> > >
> > > --
> > > 2.34.1
> > >
>
prev parent reply other threads:[~2025-12-05 1:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 7:37 [PATCH 0/4] Add Split indirect descriptors for SVQ Wafer Xie
2025-12-04 7:37 ` [PATCH 1/4] vhost: add data structure of virtio indirect descriptors in SVQ Wafer Xie
2025-12-04 7:37 ` [PATCH 2/4] vdpa: implement the interfaces alloc/free for indirect desc Wafer Xie
2025-12-04 8:41 ` Eugenio Perez Martin
2025-12-08 11:27 ` Wafer
2025-12-04 7:37 ` [PATCH 3/4] vhost: supported the virtio indirect desc of available ring Wafer Xie
2025-12-04 7:56 ` [PATCH 0/4] Add Split indirect descriptors for SVQ Jason Wang
2025-12-05 1:30 ` Wafer
2025-12-05 1:33 ` Jason Wang [this message]
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=CACGkMEvchy+JeF29VuoHHuK2XVfKdXT1_Z-HP6TS7fr8DkSusw@mail.gmail.com \
--to=jasowang@redhat.com \
--cc=angus.chen@jaguarmicro.com \
--cc=eperezma@redhat.com \
--cc=leiyang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=wafer@jaguarmicro.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).