From: Alon Levy <alevy@redhat.com>
To: qemu-devel@nongnu.org, anthony@codemonkey.ws, kraxel@redhat.com,
lcapitulino@redhat.com
Subject: [Qemu-devel] [PATCH v3 0/3] screendump async command
Date: Mon, 5 Mar 2012 17:56:26 +0200 [thread overview]
Message-ID: <1330962989-20077-1-git-send-email-alevy@redhat.com> (raw)
In-Reply-To: <4F54CEA2.10808@codemonkey.ws>
v2->v3:
pass a closure to hw_screen_dump_async
Alon Levy (3):
monitor, console: add QEVENT_SCREEN_DUMP_COMPLETE
console: add hw_screen_dump_async
add qmp screendump-async
QMP/qmp-events.txt | 15 +++++++++++
console.c | 66 ++++++++++++++++++++++++++++++++++++++++++++++++-
console.h | 9 +++++++
hw/blizzard.c | 2 +-
hw/cirrus_vga.c | 4 +-
hw/exynos4210_fimd.c | 3 +-
hw/g364fb.c | 2 +-
hw/jazz_led.c | 3 +-
hw/milkymist-vgafb.c | 2 +-
hw/musicpal.c | 2 +-
hw/omap_dss.c | 4 ++-
hw/omap_lcdc.c | 2 +-
hw/pl110.c | 2 +-
hw/pxa2xx_lcd.c | 2 +-
hw/qxl.c | 3 +-
hw/sm501.c | 4 +-
hw/ssd0303.c | 2 +-
hw/ssd0323.c | 2 +-
hw/tc6393xb.c | 1 +
hw/tcx.c | 4 +-
hw/vga-isa-mm.c | 3 +-
hw/vga-isa.c | 3 +-
hw/vga-pci.c | 3 +-
hw/vga_int.h | 1 +
hw/vmware_vga.c | 3 +-
hw/xenfb.c | 2 +
monitor.c | 7 +++++
monitor.h | 1 +
qapi-schema.json | 20 +++++++++++++++
qmp-commands.hx | 26 +++++++++++++++++++
30 files changed, 178 insertions(+), 25 deletions(-)
--
1.7.9.1
next prev parent reply other threads:[~2012-03-05 15:57 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 ` Alon Levy [this message]
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
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=1330962989-20077-1-git-send-email-alevy@redhat.com \
--to=alevy@redhat.com \
--cc=anthony@codemonkey.ws \
--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).