From: Liang Li <liang.z.li@intel.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, quintela@redhat.com,
Liang Li <liang.z.li@intel.com>,
qemu-stable@nongnu.org, yong.y.wang@intel.com,
yang.z.zhang@intel.com, stefanha@redhat.com,
amit.shah@redhat.com
Subject: [Qemu-devel] [v2 0/4] Fix long vm downtime during live migration
Date: Thu, 13 Aug 2015 13:46:32 +0800 [thread overview]
Message-ID: <1439444796-22862-1-git-send-email-liang.z.li@intel.com> (raw)
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
Liang Li (4):
migration: do cleanup operation after completion
migration: rename qemu_savevm_state_cancel
migration: rename cancel to cleanup in SaveVMHandles
migration: code clean up
include/migration/vmstate.h | 2 +-
include/sysemu/sysemu.h | 2 +-
migration/block.c | 10 ++--------
migration/migration.c | 14 +++++++-------
migration/ram.c | 10 ++--------
migration/savevm.c | 10 +++++-----
trace-events | 2 +-
7 files changed, 19 insertions(+), 31 deletions(-)
--
1.9.1
next reply other threads:[~2015-08-13 5:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 5:46 Liang Li [this message]
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 ` [Qemu-devel] [v2 0/4] Fix long vm downtime during live migration Paolo Bonzini
2015-10-09 8:56 ` 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=1439444796-22862-1-git-send-email-liang.z.li@intel.com \
--to=liang.z.li@intel.com \
--cc=amit.shah@redhat.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).