From: "Zhangjie (HZ)" <zhangjie14@huawei.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, <kvm@vger.kernel.org>
Cc: Jason Wang <jasowang@redhat.com>, <netdev@vger.kernel.org>,
<qinchuanyu@huawei.com>, <liuyongan@huawei.com>,
<davem@davemloft.net>
Subject: Re: Query: Is it possible to lose interrupts between vhost and virtio_net during migration?
Date: Tue, 5 Aug 2014 20:14:28 +0800 [thread overview]
Message-ID: <53E0CAA4.8010303@huawei.com> (raw)
In-Reply-To: <20140805094957.GB24619@redhat.com>
On 2014/8/5 17:49, Michael S. Tsirkin wrote:
> On Tue, Aug 05, 2014 at 02:29:28PM +0800, Zhangjie (HZ) wrote:
>> Jason is right, the new order is not the cause of network unreachable.
>> Changing order seems not work. After about 40 times, the problem occurs again.
>> Maybe there is other hidden reasons for that.
I modified the code to change the order myself yesterday.
This result is about my code.
>
> To make sure, you tested the patch that I posted to list:
> "vhost_net: stop guest notifiers after backend"?
>
> Please confirm.
>
OK, I will test with your patch "vhost_net: stop guest notifiers after backend".
--
Best Wishes!
Zhang Jie
next prev parent reply other threads:[~2014-08-05 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53DA2CCC.1040606@huawei.com>
[not found] ` <20140731143100.GA3834@redhat.com>
[not found] ` <20140731143725.GA3875@redhat.com>
2014-08-01 2:17 ` Query: Is it possible to lose interrupts between vhost and virtio_net during migration? Zhangjie (HZ)
[not found] ` <53DB705F.2000405@redhat.com>
[not found] ` <53DB76A9.8010305@redhat.com>
[not found] ` <53E079C8.7050700@huawei.com>
[not found] ` <20140805094957.GB24619@redhat.com>
2014-08-05 12:14 ` Zhangjie (HZ) [this message]
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=53E0CAA4.8010303@huawei.com \
--to=zhangjie14@huawei.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--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