From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by smtp.lore.kernel.org (Postfix) with ESMTP id C3B97C9830E for ; Thu, 24 Sep 2026 10:15:14 +0000 (UTC) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9E3D84026E; Thu, 24 Sep 2026 12:15:13 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id C1CF6400D7 for ; Thu, 24 Sep 2026 12:15:12 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1790244912; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=AMHDgR6jwiAZe2I+F/Or5oIT59yqfDlsZHMhxC0wzWY=; b=UDCzmERUpqfAqt4W6Au1IEfryPKh9o1StHHNkTdHpYMp+d50uivVOw+RIUF02zQ6pu/vGm 7vTNXNXxrsMYV/2jyf1H0vtDbq2JqMPuhj5lcDtpy7zGjO0CIbQyY5YvHxh4n1TstkvNeM nPQWp/iy7z8CT10ReHuc7TA1usVWe+M= Received: from mx-prod-mc-06.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-206-yAkeFrIgNEe9TVxccgCNwg-1; Thu, 24 Sep 2026 06:15:11 -0400 X-MC-Unique: yAkeFrIgNEe9TVxccgCNwg-1 X-Mimecast-MFC-AGG-ID: yAkeFrIgNEe9TVxccgCNwg_1790244910 Received: from mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.111]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 9D3E81802142; Thu, 24 Sep 2026 10:15:09 +0000 (UTC) Received: from fedora.redhat.com (unknown [10.44.32.95]) by mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id A1F3518005B5; Thu, 24 Sep 2026 10:15:06 +0000 (UTC) From: =?UTF-8?q?Eugenio=20P=C3=A9rez?= To: Maxime Coquelin Cc: dev@dpdk.org, chenbox@nvidia.com, Yongji Xie , mst@redhat.com, jasowangio@gmail.com, david.marchand@redhat.com Subject: [PATCH 0/9] Add vduse live migration features Date: Thu, 24 Sep 2026 12:14:55 +0200 Message-ID: <20260924101504.810315-1-eperezma@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.111 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: 0Jr49NM4ZlKvmm7w4cl9wLvO1t1ySTmIK9eV7I2JwIc_1790244910 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 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. 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 (3): uapi: import VDUSE and VFIO header from v7.3-rc3 kernel vhost: Support VDUSE QUEUE_READY feature vhost: Support vduse suspend feature 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 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 +- 10 files changed, 600 insertions(+), 142 deletions(-) -- 2.55.0