qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Huang, Kai" <kai.huang@linux.intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	fangying <fangying1@huawei.com>,
	"Herongguang (Stephen)" <herongguang.he@huawei.com>,
	Chris Friesen <chris.friesen@windriver.com>,
	"Han, Huaitong" <huaitong.han@intel.com>,
	"hangaohuai@huawei.com" <hangaohuai@huawei.com>,
	stable@vger.kernel.org
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"xudong.hao@linux.intel.com" <xudong.hao@linux.intel.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"wangxinxin.wang@huawei.com" <wangxinxin.wang@huawei.com>,
	"rkrcmar@redhat.com" <rkrcmar@redhat.com>,
	"guangrong.xiao@linux.intel.com" <guangrong.xiao@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration
Date: Thu, 16 Mar 2017 14:40:20 +1300	[thread overview]
Message-ID: <84e697fb-0309-faa9-9f10-90235f839db6@linux.intel.com> (raw)
In-Reply-To: <d6172fb7-ab1c-0faf-ed71-18fd74781671@redhat.com>

Thanks!

Thanks,
-Kai

On 3/14/2017 5:57 AM, Paolo Bonzini wrote:
>
>
> On 13/03/2017 15:58, fangying wrote:
>> Hi, Huang Kai
>>
>> After weeks of intensive testing, we think the problem is solved and
>> this issue can be closed.
>
> Thanks for the update.  We got to the same conclusion.
>
> Paolo
>

      reply	other threads:[~2017-03-16  1:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09 14:37 [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration Herongguang (Stephen)
2017-02-10  8:50 ` Herongguang (Stephen)
2017-02-10  9:11 ` Herongguang (Stephen)
2017-02-10 15:28   ` Chris Friesen
2017-02-10 16:14     ` Paolo Bonzini
2017-02-13 13:19     ` hangaohuai
2017-02-20  2:17     ` hangaohuai
2017-02-20  4:38       ` Han, Huaitong
2017-02-22  3:08         ` Chris Friesen
2017-02-22 11:15           ` Paolo Bonzini
2017-02-22 13:31             ` Chris Friesen
2017-02-22 14:43               ` Paolo Bonzini
2017-02-24  2:23                 ` Herongguang (Stephen)
2017-02-24  9:35                   ` Herongguang (Stephen)
2017-02-24  9:59                     ` Greg KH
2017-02-24 10:00                       ` Paolo Bonzini
2017-02-24 10:07                         ` Greg KH
2017-02-24 15:10                   ` Chris Friesen
2017-02-24 15:14                     ` Paolo Bonzini
2017-02-25  1:44                       ` Herongguang (Stephen)
2017-02-27  7:38                         ` Huang, Kai
2017-03-13 14:58                           ` fangying
2017-03-13 16:57                             ` Paolo Bonzini
2017-03-16  1:40                               ` Huang, Kai [this message]

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=84e697fb-0309-faa9-9f10-90235f839db6@linux.intel.com \
    --to=kai.huang@linux.intel.com \
    --cc=chris.friesen@windriver.com \
    --cc=fangying1@huawei.com \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=hangaohuai@huawei.com \
    --cc=herongguang.he@huawei.com \
    --cc=huaitong.han@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rkrcmar@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=wangxinxin.wang@huawei.com \
    --cc=xudong.hao@linux.intel.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).