qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel@redhat.com>
To: qemu-devel@nongnu.org
Cc: marcel@redhat.com, famz@redhat.com,
	n.nikolaev@virtualopensystems.com, mst@redhat.com
Subject: [Qemu-devel]  [PATCH] net/virtio: fix multi-queue negotiation
Date: Thu, 18 Jun 2015 21:05:44 +0300	[thread overview]
Message-ID: <1434650744-6585-1-git-send-email-marcel@redhat.com> (raw)

Clear host multi-queue related features if the peer
doesn't support it.

Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
---
Notes:
 This fixes a guest CPU soft lock, however the virtio-net
 device will not work correctly. It seems that is
 peer's "fault", not knowing how to handle the situation.
 However, I submit this patch since it corrects the negotiation
 and saves us from a guest crash (!).

 Any ideas from the virtio/multi-queue developers on how to debug
 this further are welcomed.
    
 hw/net/virtio-net.c | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
index 9281aa1..63e59e8 100644
--- a/hw/net/virtio-net.c
+++ b/hw/net/virtio-net.c
@@ -367,6 +367,11 @@ static int peer_has_ufo(VirtIONet *n)
     return n->has_ufo;
 }
 
+static int peer_has_multiqueue(VirtIONet *n)
+{
+    return n->multiqueue;
+}
+
 static void virtio_net_set_mrg_rx_bufs(VirtIONet *n, int mergeable_rx_bufs,
                                        int version_1)
 {
@@ -469,6 +474,13 @@ static uint64_t virtio_net_get_features(VirtIODevice *vdev, uint64_t features)
         virtio_clear_feature(&features, VIRTIO_NET_F_HOST_UFO);
     }
 
+    if (!peer_has_multiqueue(n)) {
+        virtio_clear_feature(&features, VIRTIO_NET_F_MQ);
+        virtio_clear_feature(&features, VIRTIO_NET_F_GUEST_ANNOUNCE);
+        virtio_clear_feature(&features, VIRTIO_NET_F_CTRL_VQ);
+        virtio_clear_feature(&features, VIRTIO_NET_F_CTRL_RX);
+    }
+
     if (!get_vhost_net(nc->peer)) {
         virtio_add_feature(&features, VIRTIO_F_VERSION_1);
         return features;
@@ -1314,7 +1326,6 @@ static void virtio_net_tx_bh(void *opaque)
 static void virtio_net_set_multiqueue(VirtIONet *n, int multiqueue)
 {
     n->multiqueue = multiqueue;
-
     virtio_net_set_queues(n);
 }
 
-- 
2.1.0

             reply	other threads:[~2015-06-18 18:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18 18:05 Marcel Apfelbaum [this message]
2015-06-23  9:57 ` [Qemu-devel] [PATCH] net/virtio: fix multi-queue negotiation Michael S. Tsirkin
2015-06-23 10:23   ` Marcel Apfelbaum
2015-06-23 10:56     ` Michael S. Tsirkin
2015-06-25 17:15       ` Marcel Apfelbaum
2015-06-24  8:00 ` Jason Wang
2015-06-25 16:54   ` Marcel Apfelbaum
2015-06-26  3:50     ` Jason Wang

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=1434650744-6585-1-git-send-email-marcel@redhat.com \
    --to=marcel@redhat.com \
    --cc=famz@redhat.com \
    --cc=mst@redhat.com \
    --cc=n.nikolaev@virtualopensystems.com \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).