From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, dgilbert@redhat.com
Subject: [Qemu-devel] [PATCH v2 00/12] Migration events + optional sections
Date: Wed, 1 Jul 2015 10:51:21 +0200 [thread overview]
Message-ID: <1435740693-10839-1-git-send-email-quintela@redhat.com> (raw)
Hi
At the end, Daved asked for a couple of things on previous series.
[v2]
- Ensure that we start in NONE even after failed/canceled migration
- move printf's to traces
- make sure that we can migrate the new states like guest-panicked
(not sure if it is a good idea to enable migrate a guest-panicked, but
it is not this series the place to forbid it)
- address all comments from Dave and Eric.
Please, review.
[v1]
As the beggining of both series have been accepted, I merged both here. Changes:
- answered all comments on list and applied suggested changes
- Use migrate_set_state() consistently
- we were misusing atomic_cmpxchg(), it didn't matter until now because
we were missing only traces, but it showed with events missing.
- Reorganized how the migration events are generated, now only on migrate_set_state.
Please review.
Juan Quintela (12):
runstate: Add runstate store
runstate: migration allows more transitions now
migration: create new section to store global state
global_state: Make section optional
vmstate: Create optional sections
migration: Add configuration section
migration: Use cmpxchg correctly
migration: ensure we start in NONE state
migration: Use always helper to set state
migration: No need to call trace_migrate_set_state()
migration: create migration event
migration: Add migration events on target side
docs/qmp/qmp-events.txt | 14 ++++
hw/i386/pc_piix.c | 2 +
hw/i386/pc_q35.c | 2 +
include/migration/migration.h | 4 ++
include/migration/vmstate.h | 2 +
include/sysemu/sysemu.h | 1 +
migration/migration.c | 157 ++++++++++++++++++++++++++++++++++++++----
migration/savevm.c | 69 +++++++++++++++++++
migration/vmstate.c | 11 +++
qapi/event.json | 12 ++++
trace-events | 4 ++
vl.c | 21 +++++-
12 files changed, 283 insertions(+), 16 deletions(-)
--
2.4.3
next reply other threads:[~2015-07-01 8:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 8:51 Juan Quintela [this message]
2015-07-01 8:51 ` [Qemu-devel] [PATCH 01/12] runstate: Add runstate store Juan Quintela
2015-07-01 8:51 ` [Qemu-devel] [PATCH 02/12] runstate: migration allows more transitions now Juan Quintela
2015-07-01 8:51 ` [Qemu-devel] [PATCH 03/12] migration: create new section to store global state Juan Quintela
2015-07-01 9:13 ` Dr. David Alan Gilbert
2015-07-01 9:34 ` Juan Quintela
2015-07-01 8:51 ` [Qemu-devel] [PATCH 04/12] global_state: Make section optional Juan Quintela
2015-07-01 9:16 ` Dr. David Alan Gilbert
2015-07-01 9:38 ` Yang Hongyang
2015-07-01 10:33 ` Juan Quintela
2015-07-01 8:51 ` [Qemu-devel] [PATCH 05/12] vmstate: Create optional sections Juan Quintela
2015-07-01 8:51 ` [Qemu-devel] [PATCH 06/12] migration: Add configuration section Juan Quintela
2015-07-01 9:47 ` Yang Hongyang
2015-07-01 10:01 ` Juan Quintela
2015-07-01 8:51 ` [Qemu-devel] [PATCH 07/12] migration: Use cmpxchg correctly Juan Quintela
2015-07-01 8:51 ` [Qemu-devel] [PATCH 08/12] migration: ensure we start in NONE state Juan Quintela
2015-07-01 9:29 ` Dr. David Alan Gilbert
2015-07-01 9:51 ` Yang Hongyang
2015-07-01 8:51 ` [Qemu-devel] [PATCH 09/12] migration: Use always helper to set state Juan Quintela
2015-07-01 9:37 ` Dr. David Alan Gilbert
2015-07-01 10:04 ` Yang Hongyang
2015-07-01 8:51 ` [Qemu-devel] [PATCH 10/12] migration: No need to call trace_migrate_set_state() Juan Quintela
2015-07-01 8:51 ` [Qemu-devel] [PATCH 11/12] migration: create migration event Juan Quintela
2015-07-01 8:51 ` [Qemu-devel] [PATCH 12/12] migration: Add migration events on target side Juan Quintela
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=1435740693-10839-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).