From: Yang Hongyang <yanghy@cn.fujitsu.com>
To: Juan Quintela <quintela@redhat.com>, qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH 08/12] migration: ensure we start in NONE state
Date: Wed, 1 Jul 2015 17:51:49 +0800 [thread overview]
Message-ID: <5593B835.5030502@cn.fujitsu.com> (raw)
In-Reply-To: <1435740693-10839-9-git-send-email-quintela@redhat.com>
On 07/01/2015 04:51 PM, Juan Quintela wrote:
> Signed-off-by: Juan Quintela <quintela@redhat.com>
> ---
> migration/migration.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/migration/migration.c b/migration/migration.c
> index cfcc227..c5b778b 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -693,7 +693,6 @@ void qmp_migrate(const char *uri, bool has_blk, bool blk,
> error_setg(errp, QERR_MIGRATION_ACTIVE);
> return;
> }
> -
suspicious blank line removal?
> if (runstate_check(RUN_STATE_INMIGRATE)) {
> error_setg(errp, "Guest is waiting for an incoming migration");
> return;
> @@ -708,6 +707,12 @@ void qmp_migrate(const char *uri, bool has_blk, bool blk,
> return;
> }
>
> + /* We are starting a new migration, so we want to start in a clean
> + state. This change is only needed if previous migration
> + failed/was cancelled. We don't use migrate_set_state() because
> + we are setting the initial state, not changing it. */
> + s->state = MIGRATION_STATUS_NONE;
> +
> s = migrate_init(¶ms);
>
> if (strstart(uri, "tcp:", &p)) {
>
--
Thanks,
Yang.
next prev parent reply other threads:[~2015-07-01 9:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 8:51 [Qemu-devel] [PATCH v2 00/12] Migration events + optional sections Juan Quintela
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 [this message]
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=5593B835.5030502@cn.fujitsu.com \
--to=yanghy@cn.fujitsu.com \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.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 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.