From: Luiz Capitulino <lcapitulino@redhat.com>
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com, quintela@redhat.com
Subject: [Qemu-devel] [PATCH 0/6] qapi: Convert migrate
Date: Fri, 10 Feb 2012 17:31:00 -0200 [thread overview]
Message-ID: <1328902266-25308-1-git-send-email-lcapitulino@redhat.com> (raw)
This is a rebase of Anthony's conversion, from his glib branch; and this is
also the beginning of the conversion of complex commands to the qapi.
There are two important changes that should be observed:
1. patch 5/6 purges the 'mon' object from migration code. One of the
consequences is that we lose the ability to print progress status to
the HMP user (esp. in block migration)
2. The HMP hmp_migrate() command is a bit tricky when in non-detached
mode: we lock the monitor and poll for the migration status from a
timer handler. This obviously assumes that migration will end at some
point
Besides, this is missing testing with libvirt. I plan to do it shortly, but
wanted to get some review in parallel.
arch_init.c | 2 +-
block-migration.c | 58 ++++++++++++++++++-----------------------
check-qdict.c | 29 ++++++++++++++++++++
error.c | 12 ++++++++
error.h | 5 +++
hmp-commands.hx | 3 +-
hmp.c | 51 ++++++++++++++++++++++++++++++++++++
hmp.h | 1 +
migration-fd.c | 2 +-
migration.c | 74 +++++++++++++++--------------------------------------
migration.h | 5 +---
monitor.c | 5 +++
monitor.h | 1 +
qapi-schema.json | 21 +++++++++++++++
qdict.c | 18 +++++++++++++
qdict.h | 1 +
qerror.c | 8 +++++
qerror.h | 6 ++++
qmp-commands.hx | 9 +-----
savevm.c | 42 ++++++++++++++---------------
sysemu.h | 11 +++----
vmstate.h | 3 +-
22 files changed, 235 insertions(+), 132 deletions(-)
next reply other threads:[~2012-02-10 19:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 19:31 Luiz Capitulino [this message]
2012-02-10 19:31 ` [Qemu-devel] [PATCH 1/6] QError: Introduce new errors for the migration command Luiz Capitulino
2012-02-15 13:10 ` Juan Quintela
2012-02-10 19:31 ` [Qemu-devel] [PATCH 2/6] monitor: Introduce qemu_get_fd() Luiz Capitulino
2012-02-15 13:11 ` Juan Quintela
2012-02-10 19:31 ` [Qemu-devel] [PATCH 3/6] QDict: Introduce qdict_copy() Luiz Capitulino
2012-02-15 13:10 ` Juan Quintela
2012-02-15 17:01 ` Luiz Capitulino
2012-02-10 19:31 ` [Qemu-devel] [PATCH 4/6] Error: Introduce error_copy() Luiz Capitulino
2012-02-15 9:04 ` Paolo Bonzini
2012-02-15 13:05 ` Luiz Capitulino
2012-02-15 13:16 ` Paolo Bonzini
2012-02-15 13:27 ` Juan Quintela
2012-02-10 19:31 ` [Qemu-devel] [PATCH 5/6] Purge migration of (almost) everything to do with monitors Luiz Capitulino
2012-02-15 9:02 ` Jan Kiszka
2012-02-15 12:53 ` Luiz Capitulino
2012-02-15 13:32 ` Jan Kiszka
2012-02-15 13:15 ` Juan Quintela
2012-02-10 19:31 ` [Qemu-devel] [PATCH 6/6] qapi: Convert migrate Luiz Capitulino
2012-02-15 9:07 ` Wen Congyang
2012-02-15 13:06 ` Luiz Capitulino
2012-02-15 13:25 ` Juan Quintela
2012-02-15 16:01 ` Michael Roth
2012-02-15 17:13 ` Luiz Capitulino
2012-02-15 13:31 ` Jan Kiszka
2012-02-15 13:44 ` Jan Kiszka
2012-02-15 8:59 ` [Qemu-devel] [PATCH 0/6] " Jan Kiszka
2012-02-15 12:49 ` Luiz Capitulino
2012-02-15 13:34 ` Jan Kiszka
2012-02-15 17:23 ` Luiz Capitulino
2012-02-15 17:39 ` Jan Kiszka
2012-02-15 17:49 ` Luiz Capitulino
2012-02-15 17:56 ` Jan Kiszka
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=1328902266-25308-1-git-send-email-lcapitulino@redhat.com \
--to=lcapitulino@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).