qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Andrew Jones <drjones@redhat.com>,
	qemu-devel@nongnu.org, armbru@redhat.com,
	Peter Xu <peterx@redhat.com>,
	lcapitulino@redhat.com, pbonzini@redhat.com,
	Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Qemu-devel] [PATCH REPOST 0/2] Add basic "detach" support for dump-guest-memory
Date: Wed, 25 Nov 2015 10:46:31 +0800	[thread overview]
Message-ID: <20151125024631.GA17946@ad.usersys.redhat.com> (raw)
In-Reply-To: <56546ADC.5050402@redhat.com>

On Tue, 11/24 06:49, Eric Blake wrote:
> On 11/24/2015 04:37 AM, Fam Zheng wrote:
> 
> >> I think the patch should be dropped, and periodic progress reports
> >> should be emitted from within the dump loops that do the heavy lifting.
> >>
> >> For the ELF format dumps, that loop appears to reside in dump_iterate()
> >> [dump.c].
> >>
> >> For the compressed format dumps, the loop seems to live in
> >> write_dump_pages() [dump.c].
> > 
> > This is a good idea!
> > 
> > What I'm not sure is where to report the progress. Can it be the monitor where
> > the dump-guest-memory command was issued? In other words, do we support raising
> > events before the previous command returns? If yes, can libvirt handle this
> > correctly? (But the worst case is using another channel to communicate the
> > progress, it is ad-hocery but it must be better than all the risk and effort to
> > enable multi-threaded dump.)
> > 
> > Eric, Markus, have any idea with the progress reporting?
> 
> I'm fairly certain we support raising events prior to completion of a
> synchronous command; what I'm not sure of is whether the event hits the
> wire right away or whether it piles up waiting for the next synchronous
> command completion.  If the latter, then we need to rework it (since the
> whole point of this exercise is that we are trying to give progress of a
> long-running synchronous command that hasn't completed yet).

So in that case we may want some "flush" operation of events. That sounds OK to
me.

> But we
> only have the one monitor connection for libvirt - the only way to pass
> events through a second channel is to open a second monitor connection,
> but that feels wrong to make libvirt have to track two monitors.

OK, that's a fair point, but FWIW I was thinking about adding an optional
argument:

    "*progress": "fd:dump-progress"

into which dump.c talks in a mini-protocol, to send progress information. It's
just an crazily hacky idea, not anything I'm advocating.

Thanks,

Fam

  reply	other threads:[~2015-11-25  2:46 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 ` [Qemu-devel] [PATCH REPOST 0/2] Add basic "detach" support for dump-guest-memory Eric Blake
2015-11-23 16:22 ` 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 [this message]
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=20151125024631.GA17946@ad.usersys.redhat.com \
    --to=famz@redhat.com \
    --cc=armbru@redhat.com \
    --cc=drjones@redhat.com \
    --cc=eblake@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=lersek@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).