From: "Eugenio Pérez" <eperezma@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, mst@redhat.com,
Yongji Xie <xieyongji@bytedance.com>,
jasowangio@gmail.com, chenbox@nvidia.com,
david.marchand@redhat.com
Subject: [PATCH v2 00/11] Add vduse live migration features
Date: Mon, 28 Sep 2026 15:29:02 +0200 [thread overview]
Message-ID: <20260928132913.1376278-1-eperezma@redhat.com> (raw)
This series introduces features to the VDUSE (vDPA Device in Userspace) driver
to support Live Migration.
Currently, DPDK does not support VDUSE devices live migration because the
driver lacks a mechanism to suspend the device and quiesce the rings to
initiate the switchover. This series implements the suspend operation to
address this limitation.
Furthermore, enabling Live Migration for devices with control virtqueue
requires two additional features. Both of them are included in this series.
* Address Spaces ID (ASID) support: This allows QEMU to isolate and intercept
the device's CVQ. By doing so, QEMU is able to migrate the device status
transparently, without requiring the device to support state save and
restore.
* QUEUE_READY: This allows QEMU to control when the dataplane virtqueues are
enabled. This ensures the dataplane is started after the device
configuration has been fully restored via the CVQ.
It also enables the VIRTIO_NET_F_STATUS feature. This allows the device to
signal the driver that it needs to send gratuitous ARP with
VIRTIO_NET_S_ANNOUNCE, reducing the Live Migration downtime.
Note that kernel headers are update to v7.3-rc3, not a stable version. This
would allow to ack the patches while the kernel uapi is published in 7.3.
v2:
* Add -D__counted_by(X)= if the compiler does not support it. It is
pulled by the kernel headers.
PATCH v1:
* Move to VDUSE_SET_FEATURES ioctl instead of config space field.
* Add a few bounds control.
* Update kernel headers to v7.3-rc3.
RFC v4:
* Sync headers with Linux's latest existing and proposed UAPI. Both
files constants and new ioctl VDUSE_SET_FEATURES.
* Check for more error conditions and clarified some error messages in
ready message processing.
* Add relevant release notes.
* Fix cosmetic whitespaces & checkpath errors.
* Fix error path of vhost_user_iotlb_init and vhost_user_iotlb_init_one.
* Fix commits author.
RFC v3:
* Replace incorrect '%lx' DEBUG print format specifier with PRIx64
RFC v2:
* Following latest comments on kernel series about VDUSE features, not checking
API version but only check if VDUSE_GET_FEATURES success.
* Move the start and last declarations in the braces as gcc 8 does not like
them interleaved with statements. Actually, I think the move was a mistake in
the first version.
https://mails.dpdk.org/archives/test-report/2026-February/958175.html
Eugenio Pérez (5):
build: define __counted_by as empty on unsupported compilers
uapi: import VDUSE and VFIO header from v7.3-rc3 kernel
vhost: Support VDUSE QUEUE_READY feature
vhost: Support vduse suspend feature
doc: add release notes for VDUSE live migration support
Maxime Coquelin (6):
vhost: introduce ASID support
vhost: add VDUSE API version negotiation
vhost: add virtqueues groups support to VDUSE
vhost: add ASID support to VDUSE IOTLB operations
vhost: claim VDUSE support for API version 1
vhost: add net status feature to VDUSE
config/meson.build | 6 +
doc/guides/rel_notes/release_26_07.rst | 8 +
kernel/linux/uapi/linux/vduse.h | 115 +++++++++++-
kernel/linux/uapi/linux/vfio.h | 91 +++++++++-
kernel/linux/uapi/version | 2 +-
lib/vhost/iotlb.c | 233 +++++++++++++++---------
lib/vhost/iotlb.h | 14 +-
lib/vhost/vduse.c | 239 +++++++++++++++++++++++--
lib/vhost/vduse.h | 3 +-
lib/vhost/vhost.c | 16 +-
lib/vhost/vhost.h | 16 +-
lib/vhost/vhost_user.c | 13 +-
12 files changed, 614 insertions(+), 142 deletions(-)
--
2.55.0
next reply other threads:[~2026-09-28 13:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 13:29 Eugenio Pérez [this message]
2026-09-28 13:29 ` [PATCH v2 01/11] build: define __counted_by as empty on unsupported compilers Eugenio Pérez
2026-09-28 23:42 ` Stephen Hemminger
2026-09-29 7:26 ` Maxime Coquelin
2026-09-28 13:29 ` [PATCH v2 02/11] uapi: import VDUSE and VFIO header from v7.3-rc3 kernel Eugenio Pérez
2026-09-28 13:29 ` [PATCH v2 03/11] vhost: introduce ASID support Eugenio Pérez
2026-09-28 13:29 ` [PATCH v2 04/11] vhost: add VDUSE API version negotiation Eugenio Pérez
2026-09-28 13:29 ` [PATCH v2 05/11] vhost: add virtqueues groups support to VDUSE Eugenio Pérez
2026-09-28 13:29 ` [PATCH v2 06/11] vhost: add ASID support to VDUSE IOTLB operations Eugenio Pérez
2026-09-28 13:29 ` [PATCH v2 07/11] vhost: claim VDUSE support for API version 1 Eugenio Pérez
2026-09-28 13:29 ` [PATCH v2 08/11] vhost: add net status feature to VDUSE Eugenio Pérez
2026-09-28 13:29 ` [PATCH v2 09/11] vhost: Support VDUSE QUEUE_READY feature Eugenio Pérez
2026-09-28 13:29 ` [PATCH v2 10/11] vhost: Support vduse suspend feature Eugenio Pérez
2026-09-28 13:29 ` [PATCH v2 11/11] doc: add release notes for VDUSE live migration support Eugenio Pérez
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=20260928132913.1376278-1-eperezma@redhat.com \
--to=eperezma@redhat.com \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jasowangio@gmail.com \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=xieyongji@bytedance.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