From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: zhanghailiang <zhang.zhanghailiang@huawei.com>
Cc: hangaohuai@huawei.com, quintela@redhat.com,
qemu-devel@nongnu.org, peter.huangpeng@huawei.com,
armbru@redhat.com, amit.shah@redhat.com, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] migration: Convert 'status' of MigrationInfo to use an enum type
Date: Wed, 4 Mar 2015 12:50:48 +0000 [thread overview]
Message-ID: <20150304125047.GF2530@work-vm> (raw)
In-Reply-To: <54F6FC8B.7030805@huawei.com>
* zhanghailiang (zhang.zhanghailiang@huawei.com) wrote:
> On 2015/3/3 16:59, Dr. David Alan Gilbert wrote:
> >* zhanghailiang (zhang.zhanghailiang@huawei.com) wrote:
> >>On 2015/3/2 23:56, Eric Blake wrote:
> >>>On 02/27/2015 07:54 PM, zhanghailiang wrote:
> >>>>On 2015/2/28 0:48, Eric Blake wrote:
> >>>>>On 02/26/2015 11:19 PM, zhanghailiang wrote:
> >>>>>>The original 'status' is an open-coded 'str' type, convert it to use an
> >>>>>>enum type.
> >>>
> >>>>>>+# @MigState:
> >>>>>
> >>>>>Do we have to abbreviate? I guess leaving it like this makes the rest
> >>>>>of the existing code base have less churn (since it matches the spelling
> >>>>>of the enum that was previous interanl only), but it might look nicer as
> >>>>
> >>>>Yes, this is the reason ..., agreed, i don't like the abbreviate,
> >>>>But there is already a 'MigrationState' type defined:
> >>>>
> >>>
> >>>>
> >>>>So, what about MigrationStatus ? ;)
> >>>
> >>>That would be fine with me.
> >>>
> >>
> >>Bad news, this name has also been used :(
> >
> >Hmm, how about 'MigrationStage' ?
>
> Er, thanks for your reply, i will follow the suggestion of Eric and Markus,
> Rename the original 'MigrationStatus' which is used internally-only.
> Keep using MigrationStatus in the new places.
>
> I will rename 'MigrationStatus' (only used for updating status of migration periodically)
> to 'MigrationDynamicStatus'. :)
OK, Since it's only used in HMP you could rename it to HMPMigrationStatus.
Dave
>
> >>In hmp.c:
> >>
> >>typedef struct MigrationStatus
> >>{
> >> QEMUTimer *timer;
> >> Monitor *mon;
> >> bool is_block_migration;
> >>} MigrationStatus
> >>
> >>
> >--
> >Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> >
> >.
> >
>
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2015-03-04 12:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 6:19 [Qemu-devel] [PATCH v2] migration: Convert 'status' of MigrationInfo to use an enum type zhanghailiang
2015-02-27 16:48 ` Eric Blake
2015-02-27 17:07 ` Dr. David Alan Gilbert
2015-02-27 17:42 ` Eric Blake
2015-02-28 3:09 ` zhanghailiang
2015-03-02 15:57 ` Eric Blake
2015-02-28 2:54 ` zhanghailiang
2015-03-02 15:56 ` Eric Blake
2015-03-03 7:15 ` zhanghailiang
2015-03-03 8:59 ` Dr. David Alan Gilbert
2015-03-04 12:37 ` zhanghailiang
2015-03-04 12:50 ` Dr. David Alan Gilbert [this message]
2015-03-04 13:01 ` zhanghailiang
2015-03-03 17:21 ` Eric Blake
2015-03-04 7:48 ` Markus Armbruster
2015-03-04 8:55 ` zhanghailiang
2015-03-04 8:52 ` zhanghailiang
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=20150304125047.GF2530@work-vm \
--to=dgilbert@redhat.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=hangaohuai@huawei.com \
--cc=lcapitulino@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=zhang.zhanghailiang@huawei.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).