From: Peter Xu <peterx@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: drjones@redhat.com, armbru@redhat.com, qemu-devel@nongnu.org,
famz@redhat.com, pbonzini@redhat.com, lcapitulino@redhat.com,
lersek@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 12/12] Dump: enhance the documentations.
Date: Tue, 1 Dec 2015 12:21:13 +0800 [thread overview]
Message-ID: <20151201042111.GJ21032@pxdev.xzpeter.org> (raw)
In-Reply-To: <565CCC2D.9050503@redhat.com>
On Mon, Nov 30, 2015 at 03:22:37PM -0700, Eric Blake wrote:
> On 11/30/2015 04:32 AM, Peter Xu wrote:
> > Add more documents to mention about "query-dump" and DUMP_COMPLETED
> > events.
> >
> > Signed-off-by: Peter Xu <peterx@redhat.com>
> > ---
> > qapi-schema.json | 7 +++++--
> > qmp-commands.hx | 4 +++-
> > 2 files changed, 8 insertions(+), 3 deletions(-)
>
> Why not squash this in to the patch that introduces the options? No
> need to have churn within the series by tweaking the documentation more
> than once.
Ok. Will do that.
>
> >
> > diff --git a/qapi-schema.json b/qapi-schema.json
> > index 577c381..ce4acb2 100644
> > --- a/qapi-schema.json
> > +++ b/qapi-schema.json
> > @@ -2115,8 +2115,11 @@
> > # 2. fd: the protocol starts with "fd:", and the following string
> > # is the fd's name.
> > #
> > -# @detach: #optional if true, QMP will return immediately rather than
> > -# waiting dump to be finished (since 2.6).
> > +# @detach: #optional if true, QMP will return immediately rather
> > +# than waiting dump to be finished. If this is specified,
> > +# user could later use "query-dump" to check latest dump
> > +# status. When dump finishes, one event DUMP_COMPLETED will
>
> s/one event DUMP_COMPLETED/a DUMP_COMPLETED event/
>
> > +# be sent to the user to notify the completion (since 2.6).
>
> s/to the user to notify the completion//
>
> > #
> > # @begin: #optional if specified, the starting physical address.
> > #
> > diff --git a/qmp-commands.hx b/qmp-commands.hx
> > index ac6d2da..cd097d4 100644
> > --- a/qmp-commands.hx
> > +++ b/qmp-commands.hx
> > @@ -858,7 +858,9 @@ Arguments:
> > - "protocol": destination file(started with "file:") or destination file
> > descriptor (started with "fd:") (json-string)
> > - "detach": if specificed, command will return immediately, without waiting
> > - for dump to be finished (json-bool)
> > + for dump to be finished. After command return, user
> > + could query for latest dump status using "query-dump". When dump
> > + finishes, an event DUMP_COMPLETED will be sent (json-bool)
>
> Awkward. How about:
>
> - "detach": if specified, the command will return immediately rather
> than waiting for the dump completion. The user can track progress with
> "query-dump", and a DUMP_COMPLETED event will occur at the end. (json-bool)
Sorry for the awkward English...
Will take your version. Thanks. :)
Peter
>
> --
> Eric Blake eblake redhat com +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
>
prev parent reply other threads:[~2015-12-01 4:21 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 11:32 [Qemu-devel] [PATCH v3 00/12] Add basic "detach" support for dump-guest-memory Peter Xu
2015-11-30 11:32 ` [Qemu-devel] [PATCH v3 01/12] dump-guest-memory: cleanup: removing dump_{error|cleanup}() Peter Xu
2015-11-30 11:32 ` [Qemu-devel] [PATCH v3 02/12] dump-guest-memory: add "detach" flag for QMP/HMP interfaces Peter Xu
2015-11-30 22:05 ` Eric Blake
2015-12-01 2:18 ` Peter Xu
2015-12-01 15:09 ` Paolo Bonzini
2015-12-02 2:31 ` Peter Xu
2015-11-30 11:32 ` [Qemu-devel] [PATCH v3 03/12] dump-guest-memory: using static DumpState, add DumpStatus Peter Xu
2015-11-30 13:00 ` Paolo Bonzini
2015-12-01 2:57 ` Peter Xu
2015-11-30 22:08 ` Eric Blake
2015-12-01 3:04 ` Peter Xu
2015-11-30 11:32 ` [Qemu-devel] [PATCH v3 04/12] dump-guest-memory: add dump_in_progress() helper function Peter Xu
2015-11-30 11:32 ` [Qemu-devel] [PATCH v3 05/12] dump-guest-memory: introduce dump_process() " Peter Xu
2015-11-30 12:55 ` Paolo Bonzini
2015-12-01 3:12 ` Peter Xu
2015-11-30 11:32 ` [Qemu-devel] [PATCH v3 06/12] dump-guest-memory: disable dump when in INMIGRATE state Peter Xu
2015-11-30 11:32 ` [Qemu-devel] [PATCH v3 07/12] dump-guest-memory: add "detach" support Peter Xu
2015-11-30 11:32 ` [Qemu-devel] [PATCH v3 08/12] dump-guest-memory: add qmp event DUMP_COMPLETED Peter Xu
2015-11-30 22:12 ` Eric Blake
2015-12-01 3:27 ` Peter Xu
2015-11-30 11:32 ` [Qemu-devel] [PATCH v3 09/12] DumpState: adding total_size and written_size fields Peter Xu
2015-11-30 11:32 ` [Qemu-devel] [PATCH v3 10/12] Dump: add qmp command "query-dump" Peter Xu
2015-11-30 12:56 ` Paolo Bonzini
2015-12-01 3:57 ` Peter Xu
2015-12-01 9:54 ` Paolo Bonzini
2015-12-01 12:32 ` Peter Xu
2015-12-01 12:37 ` Paolo Bonzini
2015-12-01 12:45 ` Peter Xu
2015-12-01 12:47 ` Paolo Bonzini
2015-12-01 13:03 ` Peter Xu
2015-11-30 22:17 ` Eric Blake
2015-12-01 4:40 ` Peter Xu
2015-12-01 13:43 ` Eric Blake
2015-11-30 11:32 ` [Qemu-devel] [PATCH v3 11/12] Dump: add hmp command "info dump" Peter Xu
2015-11-30 11:32 ` [Qemu-devel] [PATCH v3 12/12] Dump: enhance the documentations Peter Xu
2015-11-30 22:22 ` Eric Blake
2015-12-01 4:21 ` Peter Xu [this message]
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=20151201042111.GJ21032@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=drjones@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=lersek@redhat.com \
--cc=pbonzini@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).