From: Hailiang Zhang <zhang.zhanghailiang@huawei.com>
To: Eric Blake <eblake@redhat.com>, <quintela@redhat.com>,
<amit.shah@redhat.com>
Cc: <qemu-trivial@nongnu.org>, <qemu-devel@nongnu.org>,
<dgilbert@redhat.com>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] migration: fix missing assignment for has_x_checkpoint_delay
Date: Wed, 2 Nov 2016 15:26:57 +0800 [thread overview]
Message-ID: <58199541.2040909@huawei.com> (raw)
In-Reply-To: <142defcb-88bd-727f-70e4-0c8ace3f2e76@redhat.com>
On 2016/11/1 22:27, Eric Blake wrote:
> On 11/01/2016 12:50 AM, 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.
>> It doesn't influence output of hmp command 'info migrate_parameters'.
>
> Well, only because the current code doesn't forcefully assign missing
> optional parameters to any other value. But HMP was relying on
> unspecified behavior, that could have broken with any other qapi change.
>
> I might word the commit message:
>
> This also fixes the fact that HMP was relying on unspecified behavior by
> reading x_checkpoint_delay without checking has_x_checkpoint_delay.
>
> Up to the maintainer, though, since the patch itself is fine.
>
OK, thanks, I'd like to fix the message as your said :)
>>
>> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
>> ---
>> hmp.c | 1 +
>> migration/migration.c | 1 +
>> 2 files changed, 2 insertions(+)
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
prev parent reply other threads:[~2016-11-02 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 5:50 [Qemu-trivial] [PATCH] migration: fix missing assignment for has_x_checkpoint_delay zhanghailiang
2016-11-01 14:27 ` [Qemu-trivial] [Qemu-devel] " Eric Blake
2016-11-02 7:26 ` 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=58199541.2040909@huawei.com \
--to=zhang.zhanghailiang@huawei.com \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 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).