From: Gerd Hoffmann <kraxel@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Last Call for 1.5 before Hard Freeze
Date: Tue, 07 May 2013 08:35:13 +0200 [thread overview]
Message-ID: <5188A0A1.5020102@redhat.com> (raw)
In-Reply-To: <5187DC44.9060001@redhat.com>
Hi,
> And please remember to update the changelog. It's already a pretty
> featureful release, but I have no idea about what's happening in VNC
> land (LED extension and WebSockets?)
Yea, those two, I'm not aware of anything else.
> and what are the visible effects of
> Gerd's console refactorings.
Not much, for the most part it's internal cleanups, 1.6 will most likely
bring some user-visible changes building on top of the cleanups.
Most visible effect is probably that all the hops screendumping used to
go through are gone. So taking a screendump doesn't switch consoles any
more (you'll see that when typing the screendump command into a vc
terminal with sdl). Also screendumpimg doesn't need special support
from the gfx card emulation any more (which wasn't implemented by all
gfx emulation). So screendumping works with all display hardware now.
Also the screendump commands now properly throws an error in case there
is no gfx hardware installed instead of silently doing nothing.
Oh, and the threaded vnc server should finally be rock solid. display
resize used to race with the vnc threads, leading to qemu crashing on
mode switches now and then. The refactoring fixed that one too.
cheers,
Gerd
next prev parent reply other threads:[~2013-05-07 6:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 14:42 [Qemu-devel] Last Call for 1.5 before Hard Freeze Anthony Liguori
2013-05-06 16:37 ` Paolo Bonzini
2013-05-06 18:08 ` Anthony Liguori
2013-05-07 6:35 ` Gerd Hoffmann [this message]
2013-05-06 18:10 ` Michael Tokarev
2013-05-06 20:12 ` Jordan Justen
2013-05-06 20:31 ` Anthony Liguori
2013-05-06 20:41 ` Paolo Bonzini
2013-05-06 21:07 ` Jordan Justen
2013-05-07 4:40 ` Paolo Bonzini
2013-05-06 21:21 ` Jordan Justen
2013-05-06 20:45 ` Andreas Färber
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=5188A0A1.5020102@redhat.com \
--to=kraxel@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=pbonzini@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).