From: Paolo Bonzini <pbonzini@redhat.com>
To: "Zhanghaoyu (A)" <haoyu.zhang@huawei.com>
Cc: "xiaoguangrong@linux.vnet.ibm.com"
<xiaoguangrong@linux.vnet.ibm.com>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
"Huangweidong (C)" <weidong.huang@huawei.com>,
"Xiao Guangrong" <xiaoguangrong.eric@gmail.com>,
"Gleb Natapov" <gleb@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"paolo.bonzini@gmail.com" <paolo.bonzini@gmail.com>,
Xiejunyong <xiejunyong@huawei.com>,
Luonengjun <luonengjun@huawei.com>,
qemu-devel <qemu-devel@nongnu.org>, Xiahai <xiahai@huawei.com>,
Zanghongyong <zanghongyong@huawei.com>,
"Xin Rong Fu" <XRFu@novell.com>, "Yi Li" <YiLi@novell.com>,
KVM <kvm@vger.kernel.org>, "Bruce Rogers" <brogers@suse.com>,
Hanweidong <hanweidong@huawei.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] vm performance degradation after kvm live migration or save-restore with EPT enabled
Date: Thu, 08 Aug 2013 14:29:04 +0200 [thread overview]
Message-ID: <52038F10.5070900@redhat.com> (raw)
In-Reply-To: <D3E216785288A145B7BC975F83A2ED103FEF984A@szxeml556-mbx.china.huawei.com>
On 08/08/2013 01:31 PM, Zhanghaoyu (A) wrote:
> And, rebuild the kvm-kmod, then re-insmod kvm-intel.ko with ept=0,
>
> I virsh-save the VM, and then virsh-restore the VM, the performance
> degradation disappeared, and no GFN printed.
>
> But, I also made a test on the first bad
> commit(612819c3c6e67bac8fceaa7cc402f13b1b63f7e4), and applied above
> patch too,
>
> With EPT disabled, as soon as the restoring completed, the GFNs’
> flooding is starting, take some examples to show as below,
>
> but, after a period of time, only gfn = 240 printed constantly. And
> some processes restore failed, so the performance cannot be measured.
This is 0xF0000 which is the BIOS. It makes some sense, though I'm not
sure why a running OS would poke there.
It can be a useful hint, but please do as Gleb said. Try your kernel
(+kvm-kmod) with current QEMU, current kernel with your QEMU, current
kernel with current QEMU. Make a table of which kernel/QEMU combos work
and which do not. Then we can try to understand if the bug still exists
and perhaps get hints about how your vendor could backport the fix.
Paolo
next prev parent reply other threads:[~2013-08-08 12:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 11:31 [Qemu-devel] vm performance degradation after kvm live migration or save-restore with EPT enabled Zhanghaoyu (A)
2013-08-08 12:29 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-11 9:36 [Qemu-devel] vm performance degradation after kvm live migration or save-restore with ETP enabled Zhanghaoyu (A)
2013-07-11 18:20 ` Bruce Rogers
2013-07-27 7:47 ` Zhanghaoyu (A)
2013-07-29 23:47 ` Marcelo Tosatti
2013-07-30 9:04 ` Zhanghaoyu (A)
2013-08-01 6:16 ` Gleb Natapov
2013-08-05 8:35 ` [Qemu-devel] vm performance degradation after kvm live migration or save-restore with EPT enabled Zhanghaoyu (A)
2013-08-05 8:43 ` Gleb Natapov
2013-08-05 9:09 ` Zhanghaoyu (A)
2013-08-05 9:15 ` Andreas Färber
2013-08-05 9:22 ` Zhanghaoyu (A)
2013-08-05 9:37 ` Gleb Natapov
2013-08-06 10:47 ` Zhanghaoyu (A)
2013-08-07 1:34 ` Zhanghaoyu (A)
2013-08-07 5:52 ` Gleb Natapov
2013-08-14 9:05 ` Zhanghaoyu (A)
2013-08-20 13:33 ` Zhanghaoyu (A)
2013-08-31 7:45 ` Zhanghaoyu (A)
2013-08-05 18:27 ` Xiao Guangrong
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=52038F10.5070900@redhat.com \
--to=pbonzini@redhat.com \
--cc=XRFu@novell.com \
--cc=YiLi@novell.com \
--cc=afaerber@suse.de \
--cc=brogers@suse.com \
--cc=gleb@redhat.com \
--cc=hanweidong@huawei.com \
--cc=haoyu.zhang@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=luonengjun@huawei.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=paolo.bonzini@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=weidong.huang@huawei.com \
--cc=xiahai@huawei.com \
--cc=xiaoguangrong.eric@gmail.com \
--cc=xiaoguangrong@linux.vnet.ibm.com \
--cc=xiejunyong@huawei.com \
--cc=zanghongyong@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).