From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: alevy@redhat.com, Gerd Hoffmann <kraxel@redhat.com>,
lcapitulino@redhat.com
Subject: [Qemu-devel] [RfC PATCH 0/2] new screendump qmp command
Date: Mon, 17 Jun 2013 16:01:45 +0200 [thread overview]
Message-ID: <1371477707-7039-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
Just a rough + incomplete draft for now, to show the idea.
Series adds a new screendump qmp command. This does (a) allow
to specify the device we want dump from, (b) does the actual
image writing in a bottom half and (c) sends a qmp event when
(not done yet, just a comment for now).
It also adds a graphics_hw_update() variant with completion
notification (by calling a bottom half).
qxl then could stick the pointer to the notification BH into the
QXLCookie struct and schedule the BH when spice server finished
updating the screen.
Gerd Hoffmann (2):
display update with notification
console: add screendump-device qmp cmd
include/ui/console.h | 2 ++
qapi-schema.json | 15 +++++++++++
qmp-commands.hx | 25 +++++++++++++++++++
ui/console.c | 67 ++++++++++++++++++++++++++++++++++++++++++++++++++
4 files changed, 109 insertions(+)
--
1.7.9.7
next reply other threads:[~2013-06-17 14:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 14:01 Gerd Hoffmann [this message]
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
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=1371477707-7039-1-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=alevy@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).