All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: zhangchen.fnst@cn.fujitsu.com, qemu devel <qemu-devel@nongnu.org>,
	Eric Blake <eblake@redhat.com>,
	Li Zhijian <lizhijian@cn.fujitsu.com>,
	Jason Wang <jasowang@redhat.com>,
	"eddie . dong" <eddie.dong@intel.com>,
	Wen Congyang <wencongyang@gmail.com>,
	bian naimeng <biannm@cn.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH V7 2/2] Add a new qmp command to do checkpoint, query xen replication status
Date: Tue, 21 Feb 2017 20:24:55 +0800	[thread overview]
Message-ID: <3f2d885b-f4c3-e26c-348b-b3996ad5410e@cn.fujitsu.com> (raw)
In-Reply-To: <8760k3zteg.fsf@dusky.pond.sub.org>



On 02/21/2017 07:15 PM, Markus Armbruster wrote:
> Zhang Chen <zhangchen.fnst@cn.fujitsu.com> writes:
>
>> We can call this qmp command to do checkpoint outside of qemu.
>> Xen colo will need this function.
> I know nothing about "Xen colo", but I'll try anyway.
>
> I *guess* "Xen colo" is a long-running activity, and the new commands
> interact with it.  Correct?

Yes, you are right.
By the way this patch has been reviewed by Eric black.

https://lists.nongnu.org/archive/html/qemu-devel/2017-02/msg03435.html



>
>> Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
>> Signed-off-by: Wen Congyang <wencongyang@gmail.com>
>> ---
>>   migration/colo.c | 17 ++++++++++++++++
>>   qapi-schema.json | 60 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>   2 files changed, 77 insertions(+)
>>
>> diff --git a/migration/colo.c b/migration/colo.c
>> index 6fc2ade..2f98a33 100644
>> --- a/migration/colo.c
>> +++ b/migration/colo.c
>> @@ -127,6 +127,23 @@ void qmp_xen_set_replication(bool enable, bool primary,
>>       }
>>   }
>>   
>> +ReplicationResult *qmp_query_xen_replication_status(Error **errp)
>> +{
>> +    Error *err = NULL;
>> +    ReplicationResult *result = g_new0(ReplicationResult, 1);
>> +    replication_get_error_all(&err);
>> +    result->status = err ?
>> +                     REPLICATION_STATUS_ERROR :
>> +                     REPLICATION_STATUS_NORMAL;
> Reports only that there is an error, throws away the actual error
> message.  Naive question: could the error message be good to know for
> the QMP user?

Yes, Xen colo will handle it.

>
>> +    error_free(err);
>> +    return result;
>> +}
>> +
>> +void qmp_xen_do_checkpoint(Error **errp)
>> +{
>> +    replication_do_checkpoint_all(errp);
>> +}
>> +
>>   static void colo_send_message(QEMUFile *f, COLOMessage msg,
>>                                 Error **errp)
>>   {
>> diff --git a/qapi-schema.json b/qapi-schema.json
>> index 9445b93..719744a 100644
>> --- a/qapi-schema.json
>> +++ b/qapi-schema.json
>> @@ -5931,6 +5931,66 @@
>>     'data': { 'enable': 'bool', 'primary': 'bool', '*failover' : 'bool' } }
>>   
>>   ##
>> +# @ReplicationStatus:
>> +#
>> +# Describe the status of replication.
>> +#
>> +# @error: Replication has an error.
>> +#
>> +# @normal: Replication is running normally.
>> +#
>> +# Since: 2.9
>> +##
>> +{ 'enum': 'ReplicationStatus',
>> +  'data': [ 'error', 'normal' ] }
> Do you expect more status values in the future?
>
> If yes, what should clients do when they see a status value they don't
> know?

We will add other status for it, now, that's enough.

>
> If no, why not simply use bool?
>
>> +
>> +##
>> +# @ReplicationResult:
>> +#
>> +# The result format for 'query-xen-replication-status'.
>> +#
>> +# @status: enum of @ReplicationStatus, which shows current
>> +#          replication error status
>> +#
>> +# Since: 2.9
>> +##
>> +{ 'struct': 'ReplicationResult',
>> +  'data': { 'status': 'ReplicationStatus'} }
>> +
>> +##
>> +# @query-xen-replication-status:
>> +#
>> +# Query replication status while the vm is running.
>> +#
>> +# Returns: A @ReplicationResult objects showing the status.
>> +#
>> +# Example:
>> +#
>> +# -> { "execute": "query-xen-replication-status" }
>> +# <- { "return": { "status": "normal" } }
>> +#
>> +# Since: 2.9
>> +##
>> +{ 'command': 'query-xen-replication-status',
>> +  'returns': 'ReplicationResult' }
> The naming is a bit unfortunate: query-xen-replication-status returns
> ReplicationResult, which contains ReplicationStatus.

I will change the name in next version.

Thanks
Zhang Chen

>
>> +
>> +##
>> +# @xen-do-checkpoint:
>> +#
>> +# Xen uses this command to notify replication to trigger a checkpoint.
>> +#
>> +# Returns: nothing.
>> +#
>> +# Example:
>> +#
>> +# -> { "execute": "xen-do-checkpoint" }
>> +# <- { "return": {} }
>> +#
>> +# Since: 2.9
>> +##
>> +{ 'command': 'xen-do-checkpoint' }
>> +
>> +##
>>   # @GICCapability:
>>   #
>>   # The struct describes capability for a specific GIC (Generic
>
> .
>

-- 
Thanks
Zhang Chen

  reply	other threads:[~2017-02-21 12:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08  5:24 [Qemu-devel] [PATCH V7 0/2] Add new qmp commands to suppurt Xen COLO Zhang Chen
2017-02-08  5:24 ` [Qemu-devel] [PATCH V7 1/2] Add a new qmp command to start/stop replication Zhang Chen
2017-02-21 12:53   ` Hailiang Zhang
2017-02-08  5:24 ` [Qemu-devel] [PATCH V7 2/2] Add a new qmp command to do checkpoint, query xen replication status Zhang Chen
2017-02-08 21:35   ` Eric Blake
2017-02-09  2:03     ` Zhang Chen
2017-02-13 20:28     ` Stefano Stabellini
2017-02-16  3:25       ` Zhang Chen
2017-02-16  5:08         ` Jason Wang
2017-02-16  5:21           ` Zhang Chen
2017-02-21 11:15   ` Markus Armbruster
2017-02-21 12:24     ` Zhang Chen [this message]
2017-02-21 14:07       ` Markus Armbruster
2017-02-21 16:20         ` Eric Blake
2017-02-22  7:54           ` Zhang Chen
2017-02-22 15:23             ` Eric Blake
2017-02-23  6:06               ` Zhang Chen
2017-02-21 13:01   ` Hailiang Zhang
2017-02-21 13:16     ` Zhang Chen

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=3f2d885b-f4c3-e26c-348b-b3996ad5410e@cn.fujitsu.com \
    --to=zhangchen.fnst@cn.fujitsu.com \
    --cc=armbru@redhat.com \
    --cc=biannm@cn.fujitsu.com \
    --cc=eblake@redhat.com \
    --cc=eddie.dong@intel.com \
    --cc=jasowang@redhat.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wencongyang@gmail.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.