From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [5431] Allow the monitor to be suspended during non-blocking op
Date: Sun, 25 Jan 2009 20:38:23 +0100 [thread overview]
Message-ID: <497CBFAF.2090801@web.de> (raw)
In-Reply-To: <E1KmqVx-0007KU-Ek@cvs.savannah.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]
Anthony Liguori wrote:
> Revision: 5431
> http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5431
> Author: aliguori
> Date: 2008-10-06 13:52:44 +0000 (Mon, 06 Oct 2008)
>
> Log Message:
> -----------
> Allow the monitor to be suspended during non-blocking op
>
> Live migration happens in the background, but it is useful to make the monitor
> command appear as if it's blocking. This allows a management tool to
> immediately know when the live migration has completed without having to poll
> the migration status.
>
> This patch allows the monitor to be suspended from a monitor callback which
> will prevent new monitor commands from being executed.
This is not true. The current code just prevents the command prompt from
being printed. Yeah, this subsystem is hairy. :)
I'm currently reworking the whole monitor infrastructure and could
either include a fix in my series to make this true suspension - or name
the interface after its effect: monitor_enable/disable_prompt().
So, what is the actually desired behavior?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
prev parent reply other threads:[~2009-01-25 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 13:52 [Qemu-devel] [5431] Allow the monitor to be suspended during non-blocking op Anthony Liguori
2009-01-25 19:38 ` Jan Kiszka [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=497CBFAF.2090801@web.de \
--to=jan.kiszka@web.de \
--cc=anthony@codemonkey.ws \
--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).