From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Marc-André Lureau" <mlureau@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>
Subject: Re: [Qemu-devel] [PATCH/RFC 0/7] Screendump to UNIX socket & in PNG format
Date: Wed, 14 Mar 2012 12:42:36 +0100 [thread overview]
Message-ID: <4F60842C.4020107@redhat.com> (raw)
In-Reply-To: <CAJSP0QUJf6tcB2FEBEJg3hLTORmNtc7+v36n6QmppDWRxO1TVQ@mail.gmail.com>
Am 14.03.2012 10:42, schrieb Stefan Hajnoczi:
> On Tue, Mar 13, 2012 at 1:17 PM, Gerd Hoffmann <kraxel@redhat.com> wrote:
>> Hi,
>>
>>> If you want to do it as part of the QEMU codebase then a thread is
>>> probably the best way - it avoids the troubles of forking a
>>> multithreaded program and letting go of resources (guest memory, file
>>> descriptors) that aren't needed across fork.
>>
>> That pretty much requires async monitor command support though, so the
>> iothread can continue driving guest i/o while the new worker thread
>> scales/compresses/writes the screendump.
>
> The most practical first step would be simply sending the ppm over a
> socket from ppm_save(). The 'screendump' command today already blocks
> so no new badness is being added. There would be no threads or fancy
> image encoding.
Saving PNGs would be useful even without a management tool.
Kevin
next prev parent reply other threads:[~2012-03-14 11:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 13:11 [Qemu-devel] [PATCH/RFC 0/7] Screendump to UNIX socket & in PNG format Marc-André Lureau
2012-03-12 13:11 ` [Qemu-devel] [PATCH/RFC 1/7] ppm_save: use QEMUFile Marc-André Lureau
2012-03-12 13:11 ` [Qemu-devel] [PATCH/RFC 2/7] Allow a qemu_fopen_socket() to be opened for writing Marc-André Lureau
2012-03-12 13:11 ` [Qemu-devel] [PATCH/RFC 3/7] Close socket when closing QEMUFile Marc-André Lureau
2012-03-13 6:09 ` Igor Mitsyanko
2012-03-12 13:11 ` [Qemu-devel] [PATCH/RFC 4/7] Allow saving screendump to a UNIX socket Marc-André Lureau
2012-03-12 17:07 ` Daniel P. Berrange
2012-03-13 8:15 ` Gerd Hoffmann
2012-03-12 13:11 ` [Qemu-devel] [PATCH/RFC 5/7] configure: split PNG support from vnc_png feature Marc-André Lureau
2012-03-12 13:11 ` [Qemu-devel] [PATCH/RFC 6/7] Isolate color conversion from PPM handling Marc-André Lureau
2012-03-12 13:11 ` [Qemu-devel] [PATCH/RFC 7/7] Add PNG screendump Marc-André Lureau
2012-03-12 17:05 ` Daniel P. Berrange
2012-03-12 15:42 ` [Qemu-devel] [PATCH/RFC 0/7] Screendump to UNIX socket & in PNG format Eric Blake
2012-03-12 19:29 ` Marc-André Lureau
2012-03-12 17:10 ` Daniel P. Berrange
2012-03-12 18:06 ` Stefan Hajnoczi
2012-03-12 19:27 ` Marc-André Lureau
2012-03-13 10:59 ` Stefan Hajnoczi
2012-03-13 11:14 ` Marc-André Lureau
2012-03-13 11:17 ` Stefan Hajnoczi
2012-03-13 13:17 ` Gerd Hoffmann
2012-03-14 9:42 ` Stefan Hajnoczi
2012-03-14 9:51 ` Gerd Hoffmann
2012-03-14 10:01 ` Stefan Hajnoczi
2012-03-14 13:13 ` Luiz Capitulino
2012-03-14 13:19 ` Alon Levy
2012-03-14 13:28 ` Eric Blake
2012-03-14 13:36 ` Luiz Capitulino
2012-03-14 11:42 ` Kevin Wolf [this message]
2012-03-14 13:14 ` Luiz Capitulino
2012-03-12 18:53 ` Anthony Liguori
2012-03-12 18:56 ` Marc-André Lureau
2012-03-12 18:57 ` Anthony Liguori
2012-03-12 21:22 ` Michael Roth
2012-03-13 10:12 ` Jan Kiszka
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=4F60842C.4020107@redhat.com \
--to=kwolf@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=mlureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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.