On Mon, Oct 5, 2026 at 10:11 AM Maxime Coquelin <[email protected]> wrote: > > > > On Sat, Oct 3, 2026 at 11:54 AM David Marchand <[email protected]> > wrote: >> >> On Tue, 29 Sept 2026 at 12:53, Eugenio Pérez <[email protected]> wrote: >> > >> > 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. >> > >> > v3: >> > * Include uapi/linux/stddef.h and revert the -D__counted_by from v2. >> >> FYI, the issue is now fixed in main. > > > And I just re-aligned the next-virtio branch to latest main. >
Should I re-send the patches with the reviewed-by to trigger the CI etc or it is not needed?
