All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hailiang Zhang <zhang.zhanghailiang@huawei.com>
To: quintela@redhat.com, amit.shah@redhat.com
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] migration: fix missing assignment for has_x_checkpoint_delay
Date: Mon, 14 Nov 2016 10:37:04 +0800	[thread overview]
Message-ID: <58292350.5010404@huawei.com> (raw)
In-Reply-To: <1478072529-8348-1-git-send-email-zhang.zhanghailiang@huawei.com>

ping ?

On 2016/11/2 15:42, zhanghailiang wrote:
> We forgot to assign true to params->has_x_checkpoint_delay parameter
> in qmp_query_migrate_parameters.
>
> Without this, qmp command 'query-migrate-parameters' doesn't show the
> default value for x-checkpoint-delay option.
>
> This also fixes the fact that HMP was relying on unspecified behavior by
> reading x_checkpoint_delay without checking has_x_checkpoint_delay.
>
> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> ---
> v2:
> - fix the commit message as Eric sugguested.
> ---
>   hmp.c                 | 1 +
>   migration/migration.c | 1 +
>   2 files changed, 2 insertions(+)
>
> diff --git a/hmp.c b/hmp.c
> index b5e3f54..02103df 100644
> --- a/hmp.c
> +++ b/hmp.c
> @@ -318,6 +318,7 @@ void hmp_info_migrate_parameters(Monitor *mon, const QDict *qdict)
>           monitor_printf(mon, " %s: %" PRId64 " milliseconds",
>               MigrationParameter_lookup[MIGRATION_PARAMETER_DOWNTIME_LIMIT],
>               params->downtime_limit);
> +        assert(params->has_x_checkpoint_delay);
>           monitor_printf(mon, " %s: %" PRId64,
>               MigrationParameter_lookup[MIGRATION_PARAMETER_X_CHECKPOINT_DELAY],
>               params->x_checkpoint_delay);
> diff --git a/migration/migration.c b/migration/migration.c
> index e331f28..f498ab8 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -593,6 +593,7 @@ MigrationParameters *qmp_query_migrate_parameters(Error **errp)
>       params->max_bandwidth = s->parameters.max_bandwidth;
>       params->has_downtime_limit = true;
>       params->downtime_limit = s->parameters.downtime_limit;
> +    params->has_x_checkpoint_delay = true;
>       params->x_checkpoint_delay = s->parameters.x_checkpoint_delay;
>
>       return params;
>

      reply	other threads:[~2016-11-14  2:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02  7:42 [Qemu-devel] [PATCH v2] migration: fix missing assignment for has_x_checkpoint_delay zhanghailiang
2016-11-14  2:37 ` Hailiang Zhang [this message]

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=58292350.5010404@huawei.com \
    --to=zhang.zhanghailiang@huawei.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.