From: "Eugenio Pérez" <eperezma@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: chenbox@nvidia.com, jasowang@redhat.com,
david.marchand@redhat.com, dev@dpdk.org,
Yongji Xie <xieyongji@bytedance.com>,
mst@redhat.com
Subject: [RFC v3 07/10] vhost: add net status feature to VDUSE
Date: Wed, 11 Mar 2026 07:55:40 +0100 [thread overview]
Message-ID: <20260311065543.1354037-8-eperezma@redhat.com> (raw)
In-Reply-To: <20260311065543.1354037-1-eperezma@redhat.com>
From: Maxime Coquelin <maxime.coquelin@redhat.com>
Enable the VIRTIO_NET_F_STATUS feature for VDUSE devices.
This allows the device to report link status (e.g.,
VIRTIO_NET_S_LINK_UP). It also allows the device to signal the driver
that it needs to send gratuitous ARP with VIRTIO_NET_S_ANNOUNCE.
Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
---
v2:
* 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
---
lib/vhost/vduse.c | 1 +
lib/vhost/vduse.h | 3 ++-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/lib/vhost/vduse.c b/lib/vhost/vduse.c
index 80020d3d5413..54fe6cf35bc6 100644
--- a/lib/vhost/vduse.c
+++ b/lib/vhost/vduse.c
@@ -801,6 +801,7 @@ vduse_device_create(const char *path, bool compliant_ol_flags, bool extbuf, bool
goto out_ctrl_close;
}
+ vnet_config.status = VIRTIO_NET_S_LINK_UP;
vnet_config.max_virtqueue_pairs = max_queue_pairs;
memset(dev_config, 0, sizeof(struct vduse_dev_config));
diff --git a/lib/vhost/vduse.h b/lib/vhost/vduse.h
index b2515bb9df76..d697f85be5cc 100644
--- a/lib/vhost/vduse.h
+++ b/lib/vhost/vduse.h
@@ -7,7 +7,8 @@
#include "vhost.h"
-#define VDUSE_NET_SUPPORTED_FEATURES VIRTIO_NET_SUPPORTED_FEATURES
+#define VDUSE_NET_SUPPORTED_FEATURES (VIRTIO_NET_SUPPORTED_FEATURES | \
+ (1ULL << VIRTIO_NET_F_STATUS))
int vduse_device_create(const char *path, bool compliant_ol_flags, bool extbuf, bool linearbuf);
int vduse_device_destroy(const char *path);
--
2.53.0
next prev parent reply other threads:[~2026-03-11 6:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 6:55 [RFC v3 00/10] Add vduse live migration features Eugenio Pérez
2026-03-11 6:55 ` [RFC v3 01/10] uapi: align VDUSE header for ASID Eugenio Pérez
2026-03-11 6:55 ` [RFC v3 02/10] vhost: introduce ASID support Eugenio Pérez
2026-03-11 6:55 ` [RFC v3 03/10] vhost: add VDUSE API version negotiation Eugenio Pérez
2026-03-11 6:55 ` [RFC v3 04/10] vhost: add virtqueues groups support to VDUSE Eugenio Pérez
2026-03-11 6:55 ` [RFC v3 05/10] vhost: add ASID support to VDUSE IOTLB operations Eugenio Pérez
2026-03-11 6:55 ` [RFC v3 06/10] vhost: claim VDUSE support for API version 1 Eugenio Pérez
2026-03-11 6:55 ` Eugenio Pérez [this message]
2026-03-11 6:55 ` [RFC v3 08/10] uapi: Align vduse.h for enable and suspend VDUSE messages Eugenio Pérez
2026-03-11 6:55 ` [RFC v3 09/10] vhost: Support VDUSE QUEUE_READY feature Eugenio Pérez
2026-03-11 6:55 ` [RFC v3 10/10] vhost: Support vduse suspend feature Eugenio Pérez
2026-03-29 18:14 ` [RFC v3 00/10] Add vduse live migration features Stephen Hemminger
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=20260311065543.1354037-8-eperezma@redhat.com \
--to=eperezma@redhat.com \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jasowang@redhat.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