From: Eric Blake <eblake@redhat.com>
To: Peter Xu <peterx@redhat.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, armbru@redhat.com, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH REPOST 0/2] Add basic "detach" support for dump-guest-memory
Date: Mon, 23 Nov 2015 09:09:36 -0700 [thread overview]
Message-ID: <56533A40.3050102@redhat.com> (raw)
In-Reply-To: <1448273262-13845-1-git-send-email-peterx@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 755 bytes --]
On 11/23/2015 03:07 AM, Peter Xu wrote:
> Currently, dump-guest-memory supports synchronous operation only. This patch
> sets are adding "detach" support for it (just like "migrate -d" for
> migration). When "-d" is provided, dump-guest-memory command will return
> immediately without hanging user. This should be useful when the backend
> storage for the dump file is very slow.
Where is the added event that fires when the command completes? Where
can a user poll for completion if they don't want to wait for an event?
You cannot convert a blocking command to asynchronous without some
user-visible way of tracking progress.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-11-23 16:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 10:07 [Qemu-devel] [PATCH REPOST 0/2] Add basic "detach" support for dump-guest-memory Peter Xu
2015-11-23 10:07 ` [Qemu-devel] [PATCH REPOST 1/2] dump-guest-memory: add "detach" flag for QMP/HMP interfaces Peter Xu
2015-11-23 15:48 ` Andrew Jones
2015-11-23 16:10 ` Eric Blake
2015-11-24 2:40 ` Fam Zheng
2015-11-23 10:07 ` [Qemu-devel] [PATCH REPOST 2/2] dump-guest-memory: add basic "detach" support Peter Xu
2015-11-23 15:56 ` Daniel P. Berrange
2015-11-23 16:08 ` Andrew Jones
2015-11-23 16:09 ` Eric Blake [this message]
2015-11-23 16:22 ` [Qemu-devel] [PATCH REPOST 0/2] Add basic "detach" support for dump-guest-memory Laszlo Ersek
2015-11-23 17:57 ` Andrew Jones
2015-11-24 1:57 ` Peter Xu
2015-11-24 3:10 ` Fam Zheng
2015-11-24 11:14 ` Laszlo Ersek
2015-11-24 11:37 ` Fam Zheng
2015-11-24 13:49 ` Eric Blake
2015-11-25 2:46 ` Fam Zheng
2015-11-25 4:48 ` Peter Xu
2015-11-25 4:57 ` Fam Zheng
2015-11-25 8:37 ` Markus Armbruster
2015-11-24 12:05 ` Paolo Bonzini
2015-11-24 13:36 ` Laszlo Ersek
2015-11-24 14:32 ` Paolo Bonzini
2015-11-25 5:07 ` 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=56533A40.3050102@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@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).