From: "Eugenio Pérez" <eperezma@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, chenbox@nvidia.com,
Yongji Xie <xieyongji@bytedance.com>,
mst@redhat.com, jasowangio@gmail.com, david.marchand@redhat.com
Subject: [PATCH 7/9] vhost: add net status feature to VDUSE
Date: Thu, 24 Sep 2026 12:15:02 +0200 [thread overview]
Message-ID: <20260924101504.810315-8-eperezma@redhat.com> (raw)
In-Reply-To: <20260924101504.810315-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>
---
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 831614a4dabe..9a7db29b4a98 100644
--- a/lib/vhost/vduse.c
+++ b/lib/vhost/vduse.c
@@ -820,6 +820,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.55.0
next prev parent reply other threads:[~2026-09-24 10:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 10:14 [PATCH 0/9] Add vduse live migration features Eugenio Pérez
2026-09-24 10:14 ` [PATCH 1/9] uapi: import VDUSE and VFIO header from v7.3-rc3 kernel Eugenio Pérez
2026-09-24 12:32 ` Eugenio Perez Martin
2026-09-24 14:00 ` David Marchand
2026-09-24 15:37 ` Stephen Hemminger
2026-09-25 10:21 ` Eugenio Perez Martin
2026-09-24 15:38 ` Stephen Hemminger
2026-09-24 15:50 ` Maxime Coquelin
2026-09-25 9:56 ` Eugenio Perez Martin
2026-09-24 10:14 ` [PATCH 2/9] vhost: introduce ASID support Eugenio Pérez
2026-09-24 10:14 ` [PATCH 3/9] vhost: add VDUSE API version negotiation Eugenio Pérez
2026-09-24 10:14 ` [PATCH 4/9] vhost: add virtqueues groups support to VDUSE Eugenio Pérez
2026-09-24 10:15 ` [PATCH 5/9] vhost: add ASID support to VDUSE IOTLB operations Eugenio Pérez
2026-09-24 10:15 ` [PATCH 6/9] vhost: claim VDUSE support for API version 1 Eugenio Pérez
2026-09-24 10:15 ` Eugenio Pérez [this message]
2026-09-24 10:15 ` [PATCH 8/9] vhost: Support VDUSE QUEUE_READY feature Eugenio Pérez
2026-09-24 10:15 ` [PATCH 9/9] vhost: Support vduse suspend feature 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=20260924101504.810315-8-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