From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Zhang Chen <zhangckid@gmail.com>
Cc: qemu-devel@nongnu.org,
zhanghailiang <zhang.zhanghailiang@huawei.com>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] migration/colo.c: Fix compilation issue when disable replication
Date: Tue, 30 Oct 2018 19:54:30 +0000 [thread overview]
Message-ID: <20181030195430.GE2441@work-vm> (raw)
In-Reply-To: <20181024163529.15665-1-zhangckid@gmail.com>
* Zhang Chen (zhangckid@gmail.com) wrote:
> This compilation issue will occur when user use --disable-replication
> to config Qemu.
>
> Reported-by: Thomas Huth <thuth@redhat.com>
> Signed-off-by: Zhang Chen <zhangckid@gmail.com>
OK; do we need to add a check to migrate_caps_check to stop you enabling
colo in this case?
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> migration/colo.c | 18 +++++++++++++++++-
> 1 file changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/migration/colo.c b/migration/colo.c
> index 956ac236b7..b81e6ec5bb 100644
> --- a/migration/colo.c
> +++ b/migration/colo.c
> @@ -59,6 +59,8 @@ static bool colo_runstate_is_stopped(void)
>
> static void secondary_vm_do_failover(void)
> {
> +/* COLO needs enable block-replication */
> +#ifdef CONFIG_REPLICATION
> int old_state;
> MigrationIncomingState *mis = migration_incoming_get_current();
> Error *local_err = NULL;
> @@ -121,10 +123,14 @@ static void secondary_vm_do_failover(void)
> if (mis->migration_incoming_co) {
> qemu_coroutine_enter(mis->migration_incoming_co);
> }
> +#else
> + abort();
> +#endif
> }
>
> static void primary_vm_do_failover(void)
> {
> +#ifdef CONFIG_REPLICATION
> MigrationState *s = migrate_get_current();
> int old_state;
> Error *local_err = NULL;
> @@ -165,6 +171,9 @@ static void primary_vm_do_failover(void)
>
> /* Notify COLO thread that failover work is finished */
> qemu_sem_post(&s->colo_exit_sem);
> +#else
> + abort();
> +#endif
> }
>
> COLOMode get_colo_mode(void)
> @@ -373,6 +382,7 @@ static int colo_do_checkpoint_transaction(MigrationState *s,
> QIOChannelBuffer *bioc,
> QEMUFile *fb)
> {
> +#ifdef CONFIG_REPLICATION
> Error *local_err = NULL;
> int ret = -1;
>
> @@ -483,6 +493,9 @@ out:
> error_report_err(local_err);
> }
> return ret;
> +#else
> + abort();
> +#endif
> }
>
> static void colo_compare_notify_checkpoint(Notifier *notifier, void *data)
> @@ -790,13 +803,16 @@ void *colo_process_incoming_thread(void *opaque)
> qemu_mutex_unlock_iothread();
> goto out;
> }
> +#ifdef CONFIG_REPLICATION
> /* discard colo disk buffer */
> replication_do_checkpoint_all(&local_err);
> if (local_err) {
> qemu_mutex_unlock_iothread();
> goto out;
> }
> -
> +#else
> + abort();
> +#endif
> /* Notify all filters of all NIC to do checkpoint */
> colo_notify_filters_event(COLO_EVENT_CHECKPOINT, &local_err);
>
> --
> 2.17.GIT
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-10-30 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 16:35 [Qemu-devel] [PATCH] migration/colo.c: Fix compilation issue when disable replication Zhang Chen
2018-10-30 19:54 ` Dr. David Alan Gilbert [this message]
2018-11-01 2:12 ` Zhang Chen
2018-10-30 19:55 ` Dr. David Alan Gilbert
2018-10-31 16:47 ` Dr. David Alan Gilbert
2018-11-01 1:47 ` Zhang Chen
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=20181030195430.GE2441@work-vm \
--to=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=zhang.zhanghailiang@huawei.com \
--cc=zhangckid@gmail.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).