qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: qemu-devel@nongnu.org
Cc: quintela@redhat.com, aik@ozlabs.ru, Peter Lieven <pl@kamp.de>,
	owasserm@redhat.com, pbonzini@redhat.com,
	xiawenc@linux.vnet.ibm.com, david@gibson.dropbear.id.au
Subject: [Qemu-devel] [PATCHv2 0/2] fix migration of zero pages
Date: Mon, 10 Jun 2013 12:14:18 +0200	[thread overview]
Message-ID: <1370859260-8183-1-git-send-email-pl@kamp.de> (raw)

There have been reports that migration is broken on pseries by Alexey Kardashevskiy.
It turned out that migration will fail in general as soon as a page is zero on the
source, but not on the destination. I thus reverted the skipping of zero pages
in bulk transfer phase and added a patch that does not (over)write zero pages
at the destination.

v2:
 - keep skipped pages fields in monitoring and qmp intact to avoid compatiblity
   issues.

Peter Lieven (2):
  Revert "migration: do not sent zero pages in bulk stage"
  migration: do not overwrite zero pages

 arch_init.c |   27 ++++++++++++---------------
 1 file changed, 12 insertions(+), 15 deletions(-)

-- 
1.7.9.5

             reply	other threads:[~2013-06-10 10:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10 10:14 Peter Lieven [this message]
2013-06-10 10:14 ` [Qemu-devel] [PATCHv2 1/2] Revert "migration: do not sent zero pages in bulk stage" Peter Lieven
2013-06-10 15:42   ` mdroth
2013-06-10 17:08   ` Orit Wasserman
2013-06-13  2:45   ` Wenchao Xia
2013-06-10 10:14 ` [Qemu-devel] [PATCHv2 2/2] migration: do not overwrite zero pages Peter Lieven
2013-06-10 16:10   ` mdroth
2013-06-10 16:17     ` mdroth
2013-06-10 18:50     ` Peter Lieven
2013-06-10 17:13   ` Orit Wasserman
2013-06-13  3:30   ` Wenchao Xia
2013-06-13  6:21     ` Peter Lieven

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=1370859260-8183-1-git-send-email-pl@kamp.de \
    --to=pl@kamp.de \
    --cc=aik@ozlabs.ru \
    --cc=david@gibson.dropbear.id.au \
    --cc=owasserm@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=xiawenc@linux.vnet.ibm.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).