From: Kevin Wolf <kwolf@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Anthony Liguori <aliguori@us.ibm.com>,
"quintela@redhat.com" <quintela@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 3/4] Purge migration of (almost) everything to do with monitors
Date: Mon, 12 Mar 2012 15:51:04 +0100 [thread overview]
Message-ID: <4F5E0D58.7070001@redhat.com> (raw)
In-Reply-To: <20120309165721.38070eda@doriath.home>
Am 09.03.2012 20:57, schrieb Luiz Capitulino:
> On Fri, 9 Mar 2012 16:48:10 -0300
> Luiz Capitulino <lcapitulino@redhat.com> wrote:
>
>>> It's certainly possible to make the synchronous monitor command spit out status
>>> as it already uses a polling loop to determine when migration completes.
>>
>> As HMP now uses QMP as a real client, we'd have to make that information
>> available for all QMP users. Best place is probably query-migrate.
>>
>> Don't you prefer to drop the whole thing instead? :-)
>
> Oh, we actually have block migration information in query-migrate already,
> maybe we can use that to have a progress bar (not sure it's the same info
> used by current progress bar though).
>
> But dropping it is still a viable alternative :)
We should use the decoupling of the human monitor to make it better
rather than worse. :-)
Kevin
next prev parent reply other threads:[~2012-03-12 14:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 18:13 [Qemu-devel] [PATCH v2 0/4] qapi: Convert migrate Luiz Capitulino
2012-03-09 18:13 ` [Qemu-devel] [PATCH 1/4] QError: Introduce new errors for the migration command Luiz Capitulino
2012-03-09 18:13 ` [Qemu-devel] [PATCH 2/4] Error: Introduce error_copy() Luiz Capitulino
2012-03-09 18:13 ` [Qemu-devel] [PATCH 3/4] Purge migration of (almost) everything to do with monitors Luiz Capitulino
2012-03-09 18:20 ` Jan Kiszka
2012-03-09 18:30 ` Luiz Capitulino
2012-03-09 19:05 ` Jan Kiszka
2012-03-09 19:12 ` Anthony Liguori
2012-03-09 19:48 ` Luiz Capitulino
2012-03-09 19:57 ` Luiz Capitulino
2012-03-12 14:51 ` Kevin Wolf [this message]
2012-03-12 15:01 ` Luiz Capitulino
2012-03-09 18:31 ` Anthony Liguori
2012-03-09 18:45 ` Eric Blake
2012-03-09 18:53 ` Anthony Liguori
2012-03-09 19:42 ` Eric Blake
2012-03-09 19:48 ` Eric Blake
2012-03-09 18:59 ` Jan Kiszka
2012-03-09 18:13 ` [Qemu-devel] [PATCH 4/4] qapi: Convert migrate Luiz Capitulino
2012-03-09 18:26 ` Eric Blake
2012-03-09 18:33 ` Luiz Capitulino
2012-03-09 18:35 ` Anthony Liguori
2012-03-09 18:37 ` Luiz Capitulino
2012-03-09 22:51 ` Alon Levy
2012-03-12 13:21 ` Luiz Capitulino
2012-03-12 13:49 ` Alon Levy
2012-03-12 14:01 ` Luiz Capitulino
2012-03-12 14:23 ` Alon Levy
2012-03-12 14:34 ` Luiz Capitulino
-- strict thread matches above, loose matches on Subject: below --
2012-03-12 19:58 [Qemu-devel] [PATCH v3 0/4] " Luiz Capitulino
2012-03-12 19:58 ` [Qemu-devel] [PATCH 3/4] Purge migration of (almost) everything to do with monitors Luiz Capitulino
2012-03-16 19:26 [Qemu-devel] [PULL 0/4]: QMP queue Luiz Capitulino
2012-03-16 19:26 ` [Qemu-devel] [PATCH 3/4] Purge migration of (almost) everything to do with monitors Luiz Capitulino
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=4F5E0D58.7070001@redhat.com \
--to=kwolf@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.