qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: William Dauchy <william@gandi.net>
To: Jason Wang <jasowang@redhat.com>
Cc: zhangjie14@huawei.com, qemu-devel@nongnu.org,
	William Dauchy <wdauchy@gmail.com>,
	mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH V3] vhost_net: start/stop guest notifiers properly
Date: Wed, 20 Aug 2014 11:02:09 +0200	[thread overview]
Message-ID: <20140820090209.GA26555@gandi.net> (raw)
In-Reply-To: <1408424189-10510-1-git-send-email-jasowang@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]

On Aug19 12:56, Jason Wang wrote:
> commit a9f98bb5ebe6fb1869321dcc58e72041ae626ad8 vhost: multiqueue
> support changed the order of stopping the device. Previously
> vhost_dev_stop would disable backend and only afterwards, unset guest
> notifiers. We now unset guest notifiers while vhost is still
> active. This can lose interrupts causing guest networking to fail. In
> particular, this has been observed during migration.
> 
> To adapt this, several other changes are needed:
> - remove the hdev->started assertion in vhost.c since we may want to
> start the guest notifiers before vhost starts and stop the guest
> notifiers after vhost is stopped.
> - introduce the vhost_net_set_vq_index() and call it before setting
> guest notifiers. This is used to guarantee vhost_net has the correct
> virtqueue index when setting guest notifiers.
> 
> Reported-by: "Zhangjie (HZ)" <zhangjie14@huawei.com>
> Cc: William Dauchy <wdauchy@gmail.com>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> Signed-off-by: Jason Wang <jasowang@redhat.com>
> 
> --
> Changes from Michael's patch:
> - Remove the assertion
> Changes from V1:
> - Rebase to latest
> Changes from V2:
> - Introduce vhost_net_set_vq_index() to unbreak multiqueue

indeed I had with v2:
qemu-system-x86_64: hw/virtio/vhost.c:990: vhost_virtqueue_mask: Assertion `n >= hdev->vq_index && n < hdev->vq_index + hdev->nvqs' failed.

v3 seems ok to me
-- 
William

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2014-08-20  9:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19  4:56 [Qemu-devel] [PATCH V3] vhost_net: start/stop guest notifiers properly Jason Wang
2014-08-20  9:02 ` William Dauchy [this message]
2014-08-20  9:23 ` Zhangjie (HZ)
2014-08-20 10:18   ` Michael S. Tsirkin
2014-08-20 21:21     ` Michael S. Tsirkin
2014-08-21  7:37       ` Zhangjie (HZ)
2014-08-21  4:29   ` Jason Wang
2014-08-21  6:28     ` Zhangjie (HZ)
2014-08-21  6:53       ` Jason Wang
2014-08-21  7:42         ` Zhangjie (HZ)
2014-08-27 12:59           ` Michael S. Tsirkin
2014-08-29 10:40             ` Zhangjie (HZ)
2014-09-01  8:18               ` Michael S. Tsirkin
2014-09-05  8:06                 ` Zhangjie (HZ)
2014-08-22  2:56       ` Jason Wang
2014-08-27 11:54   ` Michael S. Tsirkin

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=20140820090209.GA26555@gandi.net \
    --to=william@gandi.net \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wdauchy@gmail.com \
    --cc=zhangjie14@huawei.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;
as well as URLs for NNTP newsgroup(s).