From: "Marcin Gibuła" <m.gibula@beyond.pl>
To: Liang Li <liang.z.li@intel.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, mtosatti@redhat.com
Subject: Re: [Qemu-devel] [RFC 0/2] Reduce the VM downtime about 300us
Date: Tue, 25 Aug 2015 21:25:48 +0200 [thread overview]
Message-ID: <55DCC13C.3000702@beyond.pl> (raw)
In-Reply-To: <1440481965-12318-1-git-send-email-liang.z.li@intel.com>
W dniu 2015-08-25 o 07:52, Liang Li pisze:
> This patch is for kvm live migration optimization, it fixes the issue which
> commit 317b0a6d8ba tries to fix in another way, and it can reduce the live
> migration VM downtime about 300us.
>
> *This patch is not tested for the issue commit 317b0a6d8ba tries to fix*
I'll try to test it within next few days.
--
mg
next prev parent reply other threads:[~2015-08-25 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 5:52 [Qemu-devel] [RFC 0/2] Reduce the VM downtime about 300us Liang Li
2015-08-25 5:52 ` [Qemu-devel] [RFC 1/2] kvmclock: remove cpu_synchronize_all_states call Liang Li
2015-08-25 5:52 ` [Qemu-devel] [RFC 2/2] Revert "Introduce cpu_clean_all_dirty" Liang Li
2015-08-25 19:25 ` Marcin Gibuła [this message]
2015-08-25 22:03 ` [Qemu-devel] [RFC 0/2] Reduce the VM downtime about 300us Li, Liang Z
2015-10-29 1:59 ` Li, Liang Z
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=55DCC13C.3000702@beyond.pl \
--to=m.gibula@beyond.pl \
--cc=liang.z.li@intel.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).