From: "Eugenio Pérez" <eperezma@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: Yongji Xie <xieyongji@bytedance.com>,
david.marchand@redhat.com, dev@dpdk.org, mst@redhat.com,
jasowangio@gmail.com, chenbox@nvidia.com
Subject: [RFC v4 11/11] doc: add release notes for VDUSE live migration support
Date: Tue, 7 Jul 2026 14:45:07 +0200 [thread overview]
Message-ID: <20260707124507.251729-12-eperezma@redhat.com> (raw)
In-Reply-To: <20260707124507.251729-1-eperezma@redhat.com>
Document the new VDUSE API version 1 features added to support
live migration:
- Address Space ID (ASID) support
- Virtqueue groups
- Queue ready feature (VDUSE_F_QUEUE_READY)
- Suspend feature (VDUSE_F_SUSPEND)
- Link status support (VIRTIO_NET_F_STATUS)
Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
---
doc/guides/rel_notes/release_26_07.rst | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/doc/guides/rel_notes/release_26_07.rst b/doc/guides/rel_notes/release_26_07.rst
index 6352ef27ab05..22c4da3efed6 100644
--- a/doc/guides/rel_notes/release_26_07.rst
+++ b/doc/guides/rel_notes/release_26_07.rst
@@ -131,6 +131,23 @@ New Features
to support adding and removing memory regions without resetting
the whole guest memory map.
+* **Added VDUSE API version 1 support in vhost library.**
+
+ Updated VDUSE (vDPA Device in Userspace) support with API version 1 features
+ to enable live migration:
+
+ * Added Address Space ID (ASID) support for multiple independent address spaces
+ per device, enabling better isolation and support for virtqueue groups.
+ * Added virtqueue group support to assign different virtqueues to separate
+ address spaces (e.g., control queue vs data queues).
+ * Added ``VDUSE_F_QUEUE_READY`` feature for explicit dataplane queue
+ readiness signaling, ensuring proper device initialization ordering
+ during live migration.
+ * Added ``VDUSE_F_SUSPEND`` feature to reliably suspend virtqueue processing
+ and fetch virtqueue state during live migration.
+ * Added ``VIRTIO_NET_F_STATUS`` support for link status reporting and
+ gratuitous ARP signaling in VDUSE network devices.
+
* **Added LinkData sxe2 ethernet driver.**
Added network driver for the LinkData network adapters.
--
2.55.0
prev parent reply other threads:[~2026-07-07 12:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 12:44 [RFC v4 00/11] Add vduse live migration features Eugenio Pérez
2026-07-07 12:44 ` [RFC v4 01/11] uapi: align VDUSE header for ASID Eugenio Pérez
2026-07-07 12:44 ` [RFC v4 02/11] vhost: introduce ASID support Eugenio Pérez
2026-07-07 12:44 ` [RFC v4 03/11] vhost: add VDUSE API version negotiation Eugenio Pérez
2026-07-07 12:45 ` [RFC v4 04/11] vhost: add virtqueues groups support to VDUSE Eugenio Pérez
2026-07-07 12:45 ` [RFC v4 05/11] vhost: add ASID support to VDUSE IOTLB operations Eugenio Pérez
2026-07-07 12:45 ` [RFC v4 06/11] vhost: claim VDUSE support for API version 1 Eugenio Pérez
2026-07-07 12:45 ` [RFC v4 07/11] vhost: add net status feature to VDUSE Eugenio Pérez
2026-07-07 12:45 ` [RFC v4 08/11] uapi: Align vduse.h for enable and suspend VDUSE messages Eugenio Pérez
2026-07-07 12:45 ` [RFC v4 09/11] vhost: Support VDUSE QUEUE_READY feature Eugenio Pérez
2026-07-07 12:45 ` [RFC v4 10/11] vhost: Support vduse suspend feature Eugenio Pérez
2026-07-07 12:45 ` Eugenio Pérez [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=20260707124507.251729-12-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