From: zhanghailiang <zhang.zhanghailiang@huawei.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: hangaohuai@huawei.com, quintela@redhat.com, armbru@redhat.com,
lcapitulino@redhat.com, amit.shah@redhat.com,
peter.huangpeng@huawei.com, dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 3/4] migration: Convert 'status' of MigrationInfo to use an enum type
Date: Fri, 13 Mar 2015 14:23:08 +0800 [thread overview]
Message-ID: <5502824C.1000802@huawei.com> (raw)
In-Reply-To: <5501EAFA.70103@redhat.com>
On 2015/3/13 3:37, Eric Blake wrote:
> On 03/09/2015 12:45 AM, zhanghailiang wrote:
>> The original 'status' is an open-coded 'str' type, convert it to use an
>> enum type.
>> This conversion is backwards compatible, better documented and
>> more convenient for future extensibility.
>>
>> In addition, Fix a typo for qapi-schema.json (just remove the typo) :
>> s/'completed'. 'comppleted' (since 1.2)/'completed' (since 1.2)
>>
>> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
>> ---
>> hmp.c | 7 ++++---
>> migration/migration.c | 20 +++++---------------
>> qapi-schema.json | 34 +++++++++++++++++++++++++++++-----
>> 3 files changed, 38 insertions(+), 23 deletions(-)
>
>>
>> -enum {
>> - MIGRATION_STATUS_FAILED = -1,
>> - MIGRATION_STATUS_NONE,
>
> Note that we are changing any 0-initialized struct from having
> STATUS_NONE...
>
>
>> +##
>> +{ 'enum': 'MigrationStatus',
>> + 'data': [ 'failed', 'none', 'setup', 'cancelling', 'cancelled',
>> + 'active', 'completed' ] }
>
> ...to now having status _FAILED. Fortunately, in migration/migration.c
> (the only caller prior to this conversion), I didn't spot any
> zero-initialization (migrate_get_current() returns a struct that is
> explicitly initialized to _NONE). So it looks correct.
>
Hmm, however, i think it deserves a small modification, i will adjust the place of
'failed', which i will move it to the behind of 'completed' in v5. In this way,
all of these enum type macros except 'failed' will be consistent with there original value.
>> +
>> ##
>> # @MigrationInfo
>> #
>> # Information about current migration process.
>> #
>> -# @status: #optional string describing the current migration status.
>> -# As of 0.14.0 this can be 'setup', 'active', 'completed', 'failed' or
>> -# 'cancelled'. If this field is not returned, no migration process
>> +# @status: #optional @MigState describing the current migration status.
>
> s/MigState/MigrationStatus/
>
fix in v5.
>
>> + 'data': {'*status': 'MigrationStatus', '*ram': 'MigrationStats',
>> '*disk': 'MigrationStats',
>
> Hmm. "Status" and "Stats" look awfully close to one another. But I can
> live with the two names (it's not worth a respin just for the rename).
> With the typo fix pointed out in the documentation,
>
I will keep it like that. Thanks.
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
next prev parent reply other threads:[~2015-03-13 6:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 6:45 [Qemu-devel] [PATCH v4 0/4] Convert 'status' of MigrationInfo from open-coded 'str' to enum type zhanghailiang
2015-03-09 6:45 ` [Qemu-devel] [PATCH v4 1/4] migration: Rename abbreviated macro MIG_STATE_* to MIGRATION_STATUS_* zhanghailiang
2015-03-12 19:29 ` Eric Blake
2015-03-09 6:45 ` [Qemu-devel] [PATCH v4 2/4] hmp: Rename 'MigrationStatus' to 'HMPMigrationStatus' zhanghailiang
2015-03-09 6:45 ` [Qemu-devel] [PATCH v4 3/4] migration: Convert 'status' of MigrationInfo to use an enum type zhanghailiang
2015-03-12 19:37 ` Eric Blake
2015-03-13 6:23 ` zhanghailiang [this message]
2015-03-09 6:45 ` [Qemu-devel] [PATCH v4 4/4] migration: Expose 'cancelling' status to user zhanghailiang
2015-03-13 10:49 ` Paolo Bonzini
2015-03-13 12:25 ` Eric Blake
2015-03-13 12:28 ` Dr. David Alan Gilbert
2015-03-13 13:10 ` Eric Blake
2015-03-12 1:06 ` [Qemu-devel] [PATCH v4 0/4] Convert 'status' of MigrationInfo from open-coded 'str' to enum type zhanghailiang
2015-03-12 19:30 ` [Qemu-devel] [for 2.3? PATCH " Eric Blake
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=5502824C.1000802@huawei.com \
--to=zhang.zhanghailiang@huawei.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=hangaohuai@huawei.com \
--cc=lcapitulino@redhat.com \
--cc=peter.huangpeng@huawei.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.