From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: lcapitulino@redhat.com, Alon Levy <alevy@redhat.com>,
kraxel@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 1/2] console: add hw_screen_dump_async
Date: Mon, 05 Mar 2012 12:16:23 -0600 [thread overview]
Message-ID: <4F5502F7.9000701@codemonkey.ws> (raw)
In-Reply-To: <4F54F7EA.2010705@redhat.com>
On 03/05/2012 11:29 AM, Avi Kivity wrote:
> On 03/05/2012 07:27 PM, Anthony Liguori wrote:
>> On 03/05/2012 11:20 AM, Avi Kivity wrote:
>>> On 03/05/2012 04:33 PM, Anthony Liguori wrote:
>>>>
>>>>
>>>> async in QEMU doesn't mean "generate a QMP event when you're done".
>>>> It should mean execute this closure when you finish (function pointer
>>>> + opaque).
>>>>
>>>> The QMP event should be dispatched from the closure such that the
>>>> screendump code doesn't have to have a direct dependency on QMP.
>>>>
>>>
>>> What about using the parallel execution facility of qmp? It's silly to
>>> duplicate every command X with X-async and X-COMPLETED.
>>
>> We need to switch over to QAPI to get there.
>
> Just an implementation detail, yes? No spec/protocol changes?
Correct.
>
>> We're pretty close to being there. Luiz, about how long do you
>> think before we get there?
>
> It's a pity to add new commands along the way.
It's more complicated than this unfortunately.
A client needs to be able to determine whether the 'screendump' command works as
expected. Unfortunately, when QXL was introduced, 'screendump' became broken
across multiple releases.
screendump is the right interface, but since it was broken in multiple releases,
we need another command for a client to determine that it's not broken. In the
short term, screendump_async is that. After QAPI, it will probably be a
screendump2.
I don't mind introducing short term commands and then deprecating it
particularly when they are marked as such.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2012-03-05 18:16 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 14:16 [Qemu-devel] [PATCH v2 1/2] console: add hw_screen_dump_async Alon Levy
2012-03-05 14:16 ` [Qemu-devel] [PATCH v2 2/2] add qmp screendump-async Alon Levy
2012-03-05 14:33 ` [Qemu-devel] [PATCH v2 1/2] console: add hw_screen_dump_async Anthony Liguori
2012-03-05 15:17 ` Alon Levy
2012-03-05 15:56 ` [Qemu-devel] [PATCH v3 0/3] screendump async command Alon Levy
2012-03-05 15:56 ` [Qemu-devel] [PATCH v3 1/3] monitor, console: add QEVENT_SCREEN_DUMP_COMPLETE Alon Levy
2012-03-05 15:56 ` [Qemu-devel] [PATCH v3 2/3] console: add hw_screen_dump_async Alon Levy
2012-03-05 15:56 ` [Qemu-devel] [PATCH v3 3/3] add qmp screendump-async Alon Levy
2012-03-05 17:17 ` [Qemu-devel] [PATCH v3 0/3] screendump async command Anthony Liguori
2012-03-05 17:20 ` [Qemu-devel] [PATCH v2 1/2] console: add hw_screen_dump_async Avi Kivity
2012-03-05 17:27 ` Anthony Liguori
2012-03-05 17:29 ` Avi Kivity
2012-03-05 17:56 ` Luiz Capitulino
2012-03-05 18:16 ` Anthony Liguori [this message]
2012-03-05 18:22 ` Avi Kivity
2012-03-05 19:32 ` Anthony Liguori
2012-03-05 17:31 ` Luiz Capitulino
2012-03-05 18:09 ` Alon Levy
2012-03-05 18:17 ` Avi Kivity
2012-03-05 18:58 ` Alon Levy
2012-03-05 19:45 ` Luiz Capitulino
2012-03-06 7:36 ` Gerd Hoffmann
2012-03-06 7:43 ` Alon Levy
2012-03-06 7:56 ` Alon Levy
2012-03-06 8:10 ` Gerd Hoffmann
2012-03-06 9:35 ` Alon Levy
2012-03-06 12:24 ` Luiz Capitulino
2012-03-06 13:16 ` Alon Levy
2012-03-06 13:51 ` Anthony Liguori
2012-03-06 13:53 ` Luiz Capitulino
2012-03-06 14:23 ` Alon Levy
2012-03-06 15:07 ` Anthony Liguori
2012-03-06 15:56 ` Alon Levy
2012-03-06 16:02 ` Alon Levy
2012-03-06 16:16 ` Anthony Liguori
2012-03-06 16:26 ` Alon Levy
2012-03-06 16:47 ` Anthony Liguori
2012-03-07 6:57 ` Gerd Hoffmann
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=4F5502F7.9000701@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=alevy@redhat.com \
--cc=avi@redhat.com \
--cc=kraxel@redhat.com \
--cc=lcapitulino@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).