From: Paolo Bonzini <pbonzini@redhat.com>
To: Liang Li <liang.z.li@intel.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, quintela@redhat.com,
yong.y.wang@intel.com, qemu-stable@nongnu.org,
amit.shah@redhat.com, stefanha@redhat.com,
yang.z.zhang@intel.com
Subject: Re: [Qemu-devel] [v2 0/4] Fix long vm downtime during live migration
Date: Thu, 13 Aug 2015 08:30:30 +0200 [thread overview]
Message-ID: <55CC3986.5060908@redhat.com> (raw)
In-Reply-To: <1439444796-22862-1-git-send-email-liang.z.li@intel.com>
On 13/08/2015 07:46, Liang Li wrote:
> Some cleanup operations take long time during the pause and copy stage,
> especially with the KVM patch 3ea3b7fa9af067, do these operations after
> the completion of live migration can help to reduce VM downtime.
>
> Ony the first patch changes the behavior, the rest 3 patches are for code
> cleanup.
>
> Changes:
> * Remove qemu_savevm_sate_cancel() in migrate_fd_cleanup()
> * Add 2 more patches for code clean up
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
next prev parent reply other threads:[~2015-08-13 6:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 5:46 [Qemu-devel] [v2 0/4] Fix long vm downtime during live migration Liang Li
2015-08-13 5:46 ` [Qemu-devel] [v2 1/4] migration: do cleanup operation after completion Liang Li
2015-08-13 5:46 ` [Qemu-devel] [v2 2/4] migration: rename qemu_savevm_state_cancel Liang Li
2015-08-13 5:46 ` [Qemu-devel] [v2 3/4] migration: rename cancel to cleanup in SaveVMHandles Liang Li
2015-08-13 5:46 ` [Qemu-devel] [v2 4/4] migration: code clean up Liang Li
2015-08-13 6:30 ` Paolo Bonzini [this message]
2015-10-09 8:56 ` [Qemu-devel] [v2 0/4] Fix long vm downtime during live migration Li, Liang Z
2015-10-21 9:00 ` Li, Liang Z
2015-10-26 6:09 ` Amit Shah
2015-10-26 8:27 ` 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=55CC3986.5060908@redhat.com \
--to=pbonzini@redhat.com \
--cc=amit.shah@redhat.com \
--cc=liang.z.li@intel.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.com \
--cc=yang.z.zhang@intel.com \
--cc=yong.y.wang@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).