qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, dgilbert@redhat.com
Subject: [Qemu-devel] [PULL v2 0/6] Migration pull request
Date: Wed, 15 Jul 2015 12:29:31 +0200	[thread overview]
Message-ID: <1436956177-17440-1-git-send-email-quintela@redhat.com> (raw)

Hi

[v2]
Spell Amit last name correctly.  Sorry.

Please, apply.


[v1]
This pull requset:
- small optimization by Li
- fixes global state with savevm (reported by John Snow)
- get migration traces for migration state changes even if migration
  events are not enabled
- Change state after migration has finished (reported by Christian)
- add documentation for events

Please, Apply.

PD.  Yes, it had to pass:
   make check
   virt-test
   savevm by hand


The following changes since commit 661725da09f47eb92d356fac10a4cf3b7ad1f61d:

  Merge remote-tracking branch 'remotes/cohuck/tags/s390x-20150714' into staging (2015-07-14 18:50:17 +0100)

are available in the git repository at:

  git://github.com/juanquintela/qemu.git tags/migration/20150715-1

for you to fetch changes up to 560d027b54067ffa4e79c6f7c0a499abb0d749a3:

  migration: We also want to store the global state for savevm (2015-07-15 12:22:54 +0200)

----------------------------------------------------------------
migration/next for 20150715

----------------------------------------------------------------
Juan Quintela (5):
      migration: Only change state after migration has finished
      migration: Trace event and migration event are different things
      migration: Write documetation for events capabilites
      migration: Register global state section before loadvm
      migration: We also want to store the global state for savevm

Liang Li (1):
      migration: reduce the count of strlen call

 include/migration/migration.h |  1 +
 migration/migration.c         | 52 ++++++++++++++++++++++++-------------------
 migration/ram.c               | 10 ++++-----
 migration/savevm.c            |  6 +++++
 qmp-commands.hx               |  1 +
 vl.c                          |  2 +-
 6 files changed, 43 insertions(+), 29 deletions(-)

             reply	other threads:[~2015-07-15 10:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 10:29 Juan Quintela [this message]
2015-07-15 10:29 ` [Qemu-devel] [PULL 1/6] migration: Only change state after migration has finished Juan Quintela
2015-07-15 10:29 ` [Qemu-devel] [PULL 2/6] migration: Trace event and migration event are different things Juan Quintela
2015-07-15 10:29 ` [Qemu-devel] [PULL 3/6] migration: Write documetation for events capabilites Juan Quintela
2015-07-15 10:29 ` [Qemu-devel] [PULL 4/6] migration: Register global state section before loadvm Juan Quintela
2015-07-15 10:29 ` [Qemu-devel] [PULL 5/6] migration: reduce the count of strlen call Juan Quintela
2015-07-15 10:29 ` [Qemu-devel] [PULL 6/6] migration: We also want to store the global state for savevm Juan Quintela
2015-07-15 13:18 ` [Qemu-devel] [PULL v2 0/6] Migration pull request Peter Maydell

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=1436956177-17440-1-git-send-email-quintela@redhat.com \
    --to=quintela@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=dgilbert@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).