netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Zhangjie (HZ)" <zhangjie14@huawei.com>
To: <netdev@vger.kernel.org>
Cc: <jasowang@redhat.com>, <mst@redhat.com>, <qinchuanyu@huawei.com>,
	<liuyongan@huawei.com>, <zhangjie14@huawei.com>,
	<davem@davemloft.net>
Subject: Query: Is it possible  to lose interrupts between vhost and virtio_net during migration?
Date: Thu, 31 Jul 2014 19:47:24 +0800	[thread overview]
Message-ID: <53DA2CCC.1040606@huawei.com> (raw)

[The test scenario]:

Doing migration between two Hosts roundly(A->B, B->A) ,after about 20 times, network of the VM is unreachable.
There are other 20 VMs in each Host, and they send ipv4 or ipv6 and multicast packets to each other.
Sometimes the CPU idle of the Host maybe 0;

[Problem description]:

I wonder if it was interrupts missing that cause the network unreachable.
In the migration process of kvm, source end should suspend, which include steps as follows:
1.	do_vm_stop->pause_all_vcpus
2.	vm_state_notify-> vhost_net_stop->set_guest_notifiers->kvm_virtio_pci_vq_vector_release
3.	vm_state_notify-> vhost_net_stop-> vhost_net_stop_one->OST_NET_SET_BACKEND-> vhost_net_flush_vq-> vhost_work_flush
This may cause interrupts missing. Supose the scene that, virtqueue_notify() is called in virtio_net,
then the VM is paused. And, just before the portiowrite being handled, eventfd of kvm is released.
Then, vhost could not sense the notify, and the tx notify is lost.
On the other side, if eventfd of kvm is released just after vhost_notify(), and before eventfd_signal(), then rx signal by vhost is lost.

             reply	other threads:[~2014-07-31 11:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31 11:47 Zhangjie (HZ) [this message]
2014-07-31 14:31 ` Query: Is it possible to lose interrupts between vhost and virtio_net during migration? Michael S. Tsirkin
2014-07-31 14:37   ` Michael S. Tsirkin
2014-08-01 10:47     ` Jason Wang
2014-08-01 11:14       ` Jason Wang
2014-08-05  6:29         ` Zhangjie (HZ)
2014-08-05  9:49           ` Michael S. Tsirkin
2014-08-05 12:14             ` Zhangjie (HZ)
2014-08-07 12:47               ` Zhangjie (HZ)
2014-08-14  8:52                 ` Jason Wang
2014-08-14 10:02                   ` Michael S. Tsirkin
2014-08-15  2:55                     ` Jason Wang
2014-08-17 10:22                       ` Michael S. Tsirkin
2014-08-18  5:23                         ` 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=53DA2CCC.1040606@huawei.com \
    --to=zhangjie14@huawei.com \
    --cc=davem@davemloft.net \
    --cc=jasowang@redhat.com \
    --cc=liuyongan@huawei.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=qinchuanyu@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).