From: Changlong Xie <xiecl.fnst@cn.fujitsu.com>
To: Eric Blake <eblake@redhat.com>,
qemu devel <qemu-devel@nongnu.org>,
Juan Quintela <quintela@redhat.com>,
Amit Shah <amit.shah@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
zhanghailiang <zhang.zhanghailiang@huawei.com>
Subject: Re: [Qemu-devel] [PATCH] Introduce "xen-load-devices-state"
Date: Fri, 11 Mar 2016 09:29:27 +0800 [thread overview]
Message-ID: <56E21F77.1030403@cn.fujitsu.com> (raw)
In-Reply-To: <56E1D9B3.3070908@redhat.com>
On 03/11/2016 04:31 AM, Eric Blake wrote:
> On 03/10/2016 03:23 AM, Changlong Xie wrote:
>> From: Wen Congyang <wency@cn.fujitsu.com>
>>
>> Introduce a "xen-load-devices-state" QAPI command that can be used to load
>> the state of all devices, but not the RAM or the block devices of the
>> VM.
>>
>> We only have hmp commands savevm/loadvm, and qmp commands
>> xen-save-devices-state.
>>
>> We use this new command for COLO:
>> 1. suspend both primay vm and secondary vm
>
> s/primay/primary/
Hi Eric
Will fix in next version.
>
>> 2. sync the state
>> 3. resume both primary vm and secondary vm
>>
>> In such case, we need to update all devices's state in any time.
>
> s/devices's/devices/'
Ditto.
>
>>
>> Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
>> Signed-off-by: Changlong Xie <xiecl.fnst@cn.fujitsu.com>
>> ---
>
>> +++ b/qapi-schema.json
>> @@ -4122,3 +4122,21 @@
>> ##
>> { 'enum': 'ReplayMode',
>> 'data': [ 'none', 'record', 'play' ] }
>> +
>> +##
>> +# @xen-load-devices-state:
>> +#
>> +# Load the state of all devices from file. The RAM and the block devices
>> +# of the VM are not loaded by this command.
>> +#
>> +# @filename: the file to load the state of the devices from as binary
>> +# data. See xen-save-devices-state.txt for a description of the binary
>> +# format.
>> +#
>> +# Returns: Nothing on success
>> +# If @filename cannot be opened, OpenFileFailed
>> +# If an I/O error occurs while reading the file, IOError
>
> Drop the whole Returns: paragraph. We have very few distinguished error
> categories, and you are not using anything other than a generic error
> category here (that is, OpenFileFailed and IOError are NOT valid QMP
> error categories).
>
Ditto.
>> +#
>> +# Since: 2.6
>
> You missed soft freeze; is this still 2.6 material?
>
"Since: 2.7" should be fine.
>
>> +++ b/qmp-commands.hx
>> @@ -587,6 +587,33 @@ Example:
>> EQMP
>>
>> {
>> + .name = "xen-load-devices-state",
>> + .args_type = "filename:F",
>> + .mhandler.cmd_new = qmp_marshal_xen_load_devices_state,
>> + },
>> +
>> +SQMP
>> +xen-load-devices-state
>> +-------
>
> Make the ---- separator line the same length as the text it is underlining.
>
Surely.
Thanks
-Xie
next prev parent reply other threads:[~2016-03-11 1:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 10:23 [Qemu-devel] [PATCH] Introduce "xen-load-devices-state" Changlong Xie
2016-03-10 20:31 ` Eric Blake
2016-03-11 1:29 ` Changlong Xie [this message]
2016-03-11 7:28 ` Markus Armbruster
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=56E21F77.1030403@cn.fujitsu.com \
--to=xiecl.fnst@cn.fujitsu.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.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).