From: Amit Shah <amit.shah@redhat.com>
To: gkurz@linux.vnet.ibm.com, Markus Armbruster <armbru@redhat.com>,
jjherne@linux.vnet.ibm.com,
Peter Maydell <peter.maydell@linaro.org>
Cc: qemu list <qemu-devel@nongnu.org>,
Juan Quintela <quintela@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Amit Shah <amit.shah@redhat.com>
Subject: [Qemu-devel] [PULL 0/5] migration fixes
Date: Mon, 23 May 2016 22:49:42 +0530 [thread overview]
Message-ID: <cover.1464023816.git.amit.shah@redhat.com> (raw)
The following changes since commit 65603e2fc18b48e6e55a3dd693669413141694ec:
tci: do not include exec/exec-all.h (2016-05-20 15:07:46 +0100)
are available in the git repository at:
https://git.kernel.org/pub/scm/virt/qemu/amit/migration.git tags/migration-2.7-1
for you to fetch changes up to fe904ea8242cbae2d7e69c052c754b8f5f1ba1d6:
migration: regain control of images when migration fails to complete (2016-05-23 22:19:36 +0530)
----------------------------------------------------------------
migration fixes:
- ensure src block devices continue fine after a failed migration
- fail on migration blockers; helps 9p savevm/loadvm
- move autoconverge commands out of experimental state
- move the migration-specific qjson in migration/
----------------------------------------------------------------
Greg Kurz (2):
savevm: fail if migration blockers are present
migration: regain control of images when migration fails to complete
Jason J. Herne (1):
migration: Promote improved autoconverge commands out of experimental
state
Markus Armbruster (2):
migration: Move qjson.[ch] to migration/
migration/qjson: Drop gratuitous use of QOM
Makefile.objs | 1 -
hmp.c | 28 ++++-----
include/migration/migration.h | 1 +
include/migration/qjson.h | 29 ++++++++++
include/migration/vmstate.h | 2 +-
include/qjson.h | 29 ----------
migration/Makefile.objs | 1 +
migration/migration.c | 94 ++++++++++++++++++------------
migration/qjson.c | 113 ++++++++++++++++++++++++++++++++++++
migration/ram.c | 4 +-
migration/savevm.c | 4 +-
migration/vmstate.c | 1 -
qapi-schema.json | 54 +++++++++---------
qjson.c | 129 ------------------------------------------
qmp-commands.hx | 22 +++----
tests/Makefile | 2 +-
16 files changed, 260 insertions(+), 254 deletions(-)
create mode 100644 include/migration/qjson.h
delete mode 100644 include/qjson.h
create mode 100644 migration/qjson.c
delete mode 100644 qjson.c
--
2.5.5
next reply other threads:[~2016-05-23 17:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 17:19 Amit Shah [this message]
2016-05-23 17:19 ` [Qemu-devel] [PULL 1/5] migration: Move qjson.[ch] to migration/ Amit Shah
2016-05-23 17:19 ` [Qemu-devel] [PULL 2/5] migration/qjson: Drop gratuitous use of QOM Amit Shah
2016-05-23 17:19 ` [Qemu-devel] [PULL 3/5] migration: Promote improved autoconverge commands out of experimental state Amit Shah
2016-05-23 17:19 ` [Qemu-devel] [PULL 4/5] savevm: fail if migration blockers are present Amit Shah
2016-05-26 9:46 ` Greg Kurz
2016-05-23 17:19 ` [Qemu-devel] [PULL 5/5] migration: regain control of images when migration fails to complete Amit Shah
2016-05-26 9:47 ` Greg Kurz
2016-05-24 12:05 ` [Qemu-devel] [PULL 0/5] migration fixes 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=cover.1464023816.git.amit.shah@redhat.com \
--to=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.