From: Peter Xu <peterx@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: drjones@redhat.com, lersek@redhat.com, armbru@redhat.com,
qemu-devel@nongnu.org, pbonzini@redhat.com,
lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 10/11] Dump: add qmp command "query-dump"
Date: Mon, 7 Dec 2015 15:03:09 +0800 [thread overview]
Message-ID: <20151207070309.GC2776@pxdev.xzpeter.org> (raw)
In-Reply-To: <20151207062144.GD32154@ad.usersys.redhat.com>
On Mon, Dec 07, 2015 at 02:21:44PM +0800, Fam Zheng wrote:
> On Mon, 12/07 13:56, Peter Xu wrote:
> > /* send DUMP_COMPLETED message (unconditionally) */
> > - qapi_event_send_dump_completed(!!local_err, (local_err ? \
> > + result = qmp_query_dump(NULL);
> > + /* should never fails */
>
> s/fails/fail/
Got.
>
> > diff --git a/qmp-commands.hx b/qmp-commands.hx
> > index 7b6f915..eb5bfe2 100644
> > --- a/qmp-commands.hx
> > +++ b/qmp-commands.hx
> > @@ -858,8 +858,9 @@ Arguments:
> > - "protocol": destination file(started with "file:") or destination file
> > descriptor (started with "fd:") (json-string)
> > - "detach": if specified, command will return immediately rather than waiting
> > - for the dump completion. A DUMP_COMPLETED event will occur at
> > - the end. (json-bool)
> > + for the dump completion. The user can track progress using
> > + "query-dump" A DUMP_COMPLETED event will occur at the
>
> Missing "." before "A DUMP_COMPLETED"?
Possibly... Changing both. Thanks!
Peter
>
> > + end. (json-bool)
next prev parent reply other threads:[~2015-12-07 7:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 5:56 [Qemu-devel] [PATCH v5 00/11] Add basic "detach" support for dump-guest-memory Peter Xu
2015-12-07 5:56 ` [Qemu-devel] [PATCH v5 01/11] dump-guest-memory: cleanup: removing dump_{error|cleanup}() Peter Xu
2015-12-07 5:56 ` [Qemu-devel] [PATCH v5 02/11] dump-guest-memory: add "detach" flag for QMP/HMP interfaces Peter Xu
2015-12-07 5:56 ` [Qemu-devel] [PATCH v5 03/11] dump-guest-memory: using static DumpState, add DumpStatus Peter Xu
2015-12-07 5:56 ` [Qemu-devel] [PATCH v5 04/11] dump-guest-memory: add dump_in_progress() helper function Peter Xu
2015-12-07 5:56 ` [Qemu-devel] [PATCH v5 05/11] dump-guest-memory: introduce dump_process() " Peter Xu
2015-12-07 5:56 ` [Qemu-devel] [PATCH v5 06/11] dump-guest-memory: disable dump when in INMIGRATE state Peter Xu
2015-12-07 6:14 ` Fam Zheng
2015-12-07 7:01 ` Peter Xu
2015-12-07 5:56 ` [Qemu-devel] [PATCH v5 07/11] dump-guest-memory: add "detach" support Peter Xu
2015-12-07 5:56 ` [Qemu-devel] [PATCH v5 08/11] dump-guest-memory: add qmp event DUMP_COMPLETED Peter Xu
2015-12-07 5:56 ` [Qemu-devel] [PATCH v5 09/11] DumpState: adding total_size and written_size fields Peter Xu
2015-12-07 5:56 ` [Qemu-devel] [PATCH v5 10/11] Dump: add qmp command "query-dump" Peter Xu
2015-12-07 6:21 ` Fam Zheng
2015-12-07 7:03 ` Peter Xu [this message]
2015-12-07 5:56 ` [Qemu-devel] [PATCH v5 11/11] Dump: add hmp command "info dump" Peter Xu
2015-12-07 6:23 ` [Qemu-devel] [PATCH v5 00/11] Add basic "detach" support for dump-guest-memory Fam Zheng
2015-12-07 22:13 ` Eric Blake
2015-12-08 2:26 ` Peter Xu
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=20151207070309.GC2776@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=drjones@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).