qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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,
	qemu-stable <qemu-stable@nongnu.org>,
	amit.shah@redhat.com, stefanha@redhat.com,
	yang.z.zhang@intel.com
Subject: Re: [Qemu-devel] [PATCH 0/2] Fix long vm downtime during live migration
Date: Wed, 12 Aug 2015 11:52:31 +0200	[thread overview]
Message-ID: <55CB175F.30500@redhat.com> (raw)
In-Reply-To: <1439413464-7326-1-git-send-email-liang.z.li@intel.com>



On 12/08/2015 23:04, Liang Li wrote:
> Some cleanup operations take long time during the pause and copy stage,
> especially with the KVM patch 3ea3b7fa9af067, do these operation after
> the completion of live migration can help to reduce VM downtime.
> 
> 
> Liang Li (2):
>   migration: do cleanup operation after completion
>   migration: rename qemu_savevm_state_cancel
> 
>  include/sysemu/sysemu.h | 2 +-
>  migration/block.c       | 1 -
>  migration/migration.c   | 7 +++++--
>  migration/ram.c         | 1 -
>  migration/savevm.c      | 6 +++---
>  trace-events            | 2 +-
>  6 files changed, 10 insertions(+), 9 deletions(-)
> 

That's really a clever solution!

Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-stable@nongnu.org

  reply	other threads:[~2015-08-12  9:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 21:04 [Qemu-devel] [PATCH 0/2] Fix long vm downtime during live migration Liang Li
2015-08-12  9:52 ` Paolo Bonzini [this message]
2015-08-12 21:04 ` [Qemu-devel] [PATCH 1/2] migration: do cleanup operation after completion Liang Li
2015-08-12  9:55   ` Paolo Bonzini
2015-08-12 11:11     ` Li, Liang Z
2015-08-12 21:04 ` [Qemu-devel] [PATCH 2/2] migration: rename qemu_savevm_state_cancel Liang Li

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=55CB175F.30500@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 \
    /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).