From: Gerd Hoffmann <kraxel@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
alevy@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [RfC PATCH 2/2] console: add screendump-device qmp cmd
Date: Tue, 18 Jun 2013 15:24:33 +0200 [thread overview]
Message-ID: <51C05F91.6020201@redhat.com> (raw)
In-Reply-To: <20130618091323.26c2988b@redhat.com>
Hi,
>> Something like the attached patch? Which is just the bare minimum I'll
>> need for screendump. Basically a one-off bottom half with some monitor
>> infrastructure (job id, error handling). So it isn't for big jobs, but
>> for small jobs which have to wait for something before they execute
>> (spice-server, guest action, whatever).
>
> I only skimmed over the patch, but you need QMP commands to cancel
> and to query running jobs.
Sure, can easily go on top, just need to stuff the monitor_jobs into a
list and allow ops on it. Just want to make sure the direction I'm
heading to is fine.
> Also, please move all this stuff to qmp.c
> and do s/monitor/qmp rename.
Will do.
> Lastly, is it possible to have the block job QMP API on top of this
> new QMP job API?
Don't think so. As mentioned above this does short-running jobs as
bottom half whereas block jobs are running in coroutines ...
cheers,
Gerd
next prev parent reply other threads:[~2013-06-18 13:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 14:01 [Qemu-devel] [RfC PATCH 0/2] new screendump qmp command Gerd Hoffmann
2013-06-17 14:01 ` [Qemu-devel] [RfC PATCH 1/2] display update with notification Gerd Hoffmann
2013-06-17 14:39 ` Anthony Liguori
2013-06-17 14:01 ` [Qemu-devel] [RfC PATCH 2/2] console: add screendump-device qmp cmd Gerd Hoffmann
2013-06-17 14:43 ` Anthony Liguori
2013-06-17 14:50 ` Luiz Capitulino
2013-06-18 9:24 ` Gerd Hoffmann
2013-06-18 13:13 ` Luiz Capitulino
2013-06-18 13:24 ` Gerd Hoffmann [this message]
2013-06-18 14:47 ` Stefan Hajnoczi
2013-06-25 10:28 ` Gerd Hoffmann
2013-07-12 17:01 ` Eric Blake
2013-07-12 17:06 ` Eric Blake
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=51C05F91.6020201@redhat.com \
--to=kraxel@redhat.com \
--cc=alevy@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 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).