From: Paolo Bonzini <pbonzini@redhat.com>
To: Chris Friesen <chris.friesen@windriver.com>
Cc: "Herongguang (Stephen)" <herongguang.he@huawei.com>,
rkrcmar@redhat.com, kvm@vger.kernel.org, qemu-devel@nongnu.org,
fangying1@huawei.com, "wangxin (U)" <wangxinxin.wang@huawei.com>
Subject: Re: kvm bug in __rmap_clear_dirty during live migration
Date: Fri, 10 Feb 2017 11:14:59 -0500 (EST) [thread overview]
Message-ID: <1847999171.20327674.1486743299204.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <589DDC05.9010807@windriver.com>
> Well, not so much solved as worked around it.
>
> It seems that the problem only showed up on Broadwell, which made us wonder
> about something hardware specific.
Yes, the bug seems to be related to PML. I am looking at the code,
but I haven't found anything yet.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Chris Friesen <chris.friesen@windriver.com>
Cc: "Herongguang (Stephen)" <herongguang.he@huawei.com>,
rkrcmar@redhat.com, kvm@vger.kernel.org, qemu-devel@nongnu.org,
fangying1@huawei.com, "wangxin (U)" <wangxinxin.wang@huawei.com>
Subject: Re: [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration
Date: Fri, 10 Feb 2017 11:14:59 -0500 (EST) [thread overview]
Message-ID: <1847999171.20327674.1486743299204.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <589DDC05.9010807@windriver.com>
> Well, not so much solved as worked around it.
>
> It seems that the problem only showed up on Broadwell, which made us wonder
> about something hardware specific.
Yes, the bug seems to be related to PML. I am looking at the code,
but I haven't found anything yet.
Paolo
next prev parent reply other threads:[~2017-02-10 16:15 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 14:37 kvm bug in __rmap_clear_dirty during live migration Herongguang (Stephen)
2017-02-09 14:37 ` [Qemu-devel] " Herongguang (Stephen)
2017-02-10 8:50 ` Herongguang (Stephen)
2017-02-10 8:50 ` [Qemu-devel] " Herongguang (Stephen)
2017-02-10 9:11 ` Herongguang (Stephen)
2017-02-10 9:11 ` [Qemu-devel] " Herongguang (Stephen)
2017-02-10 15:28 ` Chris Friesen
2017-02-10 15:28 ` [Qemu-devel] " Chris Friesen
2017-02-10 16:14 ` Paolo Bonzini [this message]
2017-02-10 16:14 ` Paolo Bonzini
2017-02-13 13:19 ` hangaohuai
2017-02-13 13:19 ` hangaohuai
2017-02-20 2:17 ` hangaohuai
2017-02-20 2:17 ` [Qemu-devel] " 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 2:23 ` Herongguang (Stephen)
2017-02-24 9:35 ` 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 10:07 ` [Qemu-devel] " Greg KH
2017-02-24 15:10 ` Chris Friesen
2017-02-24 15:10 ` Chris Friesen
2017-02-24 15:14 ` Paolo Bonzini
2017-02-24 15:14 ` [Qemu-devel] " Paolo Bonzini
2017-02-25 1:44 ` Herongguang (Stephen)
2017-02-25 1:44 ` Herongguang (Stephen)
2017-02-27 7:38 ` Huang, Kai
2017-02-27 7:38 ` [Qemu-devel] " Huang, Kai
2017-03-13 14:58 ` fangying
2017-03-13 14:58 ` fangying
2017-03-13 16:57 ` Paolo Bonzini
2017-03-16 1:40 ` Huang, Kai
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=1847999171.20327674.1486743299204.JavaMail.zimbra@redhat.com \
--to=pbonzini@redhat.com \
--cc=chris.friesen@windriver.com \
--cc=fangying1@huawei.com \
--cc=herongguang.he@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.com \
--cc=wangxinxin.wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.