From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: mst@redhat.com, jasowang@redhat.com,
virtualization@lists.linux-foundation.org,
Willem de Bruijn <willemb@google.com>
Subject: [PATCH RFC 2/2] virtio_net: enable probing for NEEDS_RESET support
Date: Tue, 29 Aug 2017 16:07:59 -0400 [thread overview]
Message-ID: <20170829200759.13975-3-willemdebruijn.kernel@gmail.com> (raw)
In-Reply-To: <20170829200759.13975-1-willemdebruijn.kernel@gmail.com>
From: Willem de Bruijn <willemb@google.com>
Implement a mechanism to signal that a virtio device implements the
VIRTIO_CONFIG_S_NEEDS_RESET command.
Testing for VIRTIO_CONFIG_S_NEEDS_RESET support by issuing the request
and verifying the reset state would require an expensive state change.
To avoid that, add a status bit to the feature register used during
feature negotiation between host and guest.
Set the bit for virtio-net, which supports the feature.
Signed-off-by: Willem de Bruijn <willemb@google.com>
---
drivers/net/virtio_net.c | 2 ++
include/uapi/linux/virtio_config.h | 3 +++
2 files changed, 5 insertions(+)
diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
index 5e349226f7c1..15483a982106 100644
--- a/drivers/net/virtio_net.c
+++ b/drivers/net/virtio_net.c
@@ -2801,12 +2801,14 @@ static struct virtio_device_id id_table[] = {
static unsigned int features[] = {
VIRTNET_FEATURES,
+ VIRTIO_F_CAN_RESET,
};
static unsigned int features_legacy[] = {
VIRTNET_FEATURES,
VIRTIO_NET_F_GSO,
VIRTIO_F_ANY_LAYOUT,
+ VIRTIO_F_CAN_RESET,
};
static struct virtio_driver virtio_net_driver = {
diff --git a/include/uapi/linux/virtio_config.h b/include/uapi/linux/virtio_config.h
index 308e2096291f..726be44a04d3 100644
--- a/include/uapi/linux/virtio_config.h
+++ b/include/uapi/linux/virtio_config.h
@@ -56,6 +56,9 @@
* suppressed them? */
#define VIRTIO_F_NOTIFY_ON_EMPTY 24
+/* Driver supports the VIRTIO_CONFIG_S_NEEDS_RESET command */
+#define VIRTIO_F_CAN_RESET 25
+
/* Can the device handle any descriptor layout? */
#define VIRTIO_F_ANY_LAYOUT 27
#endif /* VIRTIO_CONFIG_NO_LEGACY */
--
2.14.1.342.g6490525c54-goog
next prev parent reply other threads:[~2017-08-29 20:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 20:07 [PATCH RFC 0/2] virtio-net: implement reset request Willem de Bruijn
2017-08-29 20:07 ` [PATCH RFC 1/2] virtio_net: implement VIRTIO_CONFIG_S_NEEDS_RESET Willem de Bruijn
2017-08-29 20:20 ` Michael S. Tsirkin
2017-08-29 20:20 ` Michael S. Tsirkin
2017-10-05 16:18 ` Willem de Bruijn
2017-10-05 16:18 ` Willem de Bruijn
2017-08-29 20:07 ` Willem de Bruijn
2017-08-29 20:07 ` Willem de Bruijn [this message]
2017-08-29 20:16 ` [PATCH RFC 2/2] virtio_net: enable probing for NEEDS_RESET support Michael S. Tsirkin
2017-08-29 20:27 ` Willem de Bruijn
2017-08-29 20:38 ` Michael S. Tsirkin
2017-08-29 21:02 ` Willem de Bruijn
2017-08-29 21:02 ` [virtio-dev] " Willem de Bruijn
2017-08-29 21:02 ` Willem de Bruijn
2017-08-29 21:13 ` Michael S. Tsirkin
2017-08-29 21:13 ` [virtio-dev] " Michael S. Tsirkin
2017-08-29 21:13 ` Michael S. Tsirkin
2017-08-29 22:38 ` Willem de Bruijn
2017-08-29 22:38 ` [virtio-dev] " Willem de Bruijn
2017-08-29 22:38 ` Willem de Bruijn
2017-08-29 20:38 ` Michael S. Tsirkin
2017-08-29 20:27 ` Willem de Bruijn
2017-08-29 20:07 ` Willem de Bruijn
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=20170829200759.13975-3-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=willemb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.