From: Hailiang Zhang <zhang.zhanghailiang@huawei.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/3] COLO: Define COLOMode without QAPI
Date: Sat, 29 Jul 2017 14:49:34 +0800 [thread overview]
Message-ID: <597C2FFE.5020405@huawei.com> (raw)
In-Reply-To: <20170728171731.GB3008@work-vm>
On 2017/7/29 1:17, Dr. David Alan Gilbert wrote:
> * Markus Armbruster (armbru@redhat.com) wrote:
>> COLOMode is defined in the QAPI schema, but not used there. Of the
>> stuff QAPI generates for it only the typedef is actually used. Use of
>> QAPI is pointless and only complicates things, so don't.
> Hmm, in one of the old COLO worlds I have, there's code to emit an event
> on exiting from COLO and that event includes the mode it was in.
Yes, we need it in the later series.
> If the intent is to bring that or similar back then it would be worth
> keeping.
Agreed. ;)
> Dave
>
>> Cc: zhanghailiang <zhang.zhanghailiang@huawei.com>
>> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>> ---
>> include/migration/colo.h | 6 ++++++
>> qapi-schema.json | 16 ----------------
>> 2 files changed, 6 insertions(+), 16 deletions(-)
>>
>> diff --git a/include/migration/colo.h b/include/migration/colo.h
>> index ff9874e..5d7c500 100644
>> --- a/include/migration/colo.h
>> +++ b/include/migration/colo.h
>> @@ -26,6 +26,12 @@ void migration_incoming_exit_colo(void);
>> void *colo_process_incoming_thread(void *opaque);
>> bool migration_incoming_in_colo_state(void);
>>
>> +typedef enum {
>> + COLO_MODE_UNKNOWN,
>> + COLO_MODE_PRIMARY,
>> + COLO_MODE_SECONDARY,
>> +} COLOMode;
>> +
>> COLOMode get_colo_mode(void);
>>
>> /* failover */
>> diff --git a/qapi-schema.json b/qapi-schema.json
>> index 9b6f6cb..3f0eb05 100644
>> --- a/qapi-schema.json
>> +++ b/qapi-schema.json
>> @@ -1304,22 +1304,6 @@
>> 'vmstate-loaded' ] }
>>
>> ##
>> -# @COLOMode:
>> -#
>> -# The colo mode
>> -#
>> -# @unknown: unknown mode
>> -#
>> -# @primary: master side
>> -#
>> -# @secondary: slave side
>> -#
>> -# Since: 2.8
>> -##
>> -{ 'enum': 'COLOMode',
>> - 'data': [ 'unknown', 'primary', 'secondary'] }
>> -
>> -##
>> # @FailoverStatus:
>> #
>> # An enumeration of COLO failover status
>> --
>> 2.7.5
>>
>>
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>
> .
>
next prev parent reply other threads:[~2017-07-29 6:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 13:45 [Qemu-devel] [PATCH 0/3] Don't QAPI without need Markus Armbruster
2017-07-28 13:45 ` [Qemu-devel] [PATCH 1/3] replay: Define ReplayMode without QAPI Markus Armbruster
2017-07-31 6:59 ` Pavel Dovgalyuk
2017-07-31 13:13 ` Markus Armbruster
2017-07-31 13:30 ` Pavel Dovgalyuk
2017-07-28 13:45 ` [Qemu-devel] [PATCH 2/3] COLO: Define COLOMode " Markus Armbruster
2017-07-28 17:17 ` Dr. David Alan Gilbert
2017-07-28 18:07 ` Eric Blake
2017-07-31 9:02 ` Markus Armbruster
2017-07-29 6:49 ` Hailiang Zhang [this message]
2017-07-28 13:45 ` [Qemu-devel] [PATCH 3/3] block: Remove unused BlockDeviceMapEntry Markus Armbruster
2017-07-28 18:10 ` Eric Blake
2017-12-15 13:13 ` Max Reitz
2017-07-28 18:10 ` [Qemu-devel] [PATCH 0/3] Don't QAPI without need 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=597C2FFE.5020405@huawei.com \
--to=zhang.zhanghailiang@huawei.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).