qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 6/6] kvm: qemu: fix vga screendump
Date: Sun, 20 Jul 2008 13:39:55 -0500	[thread overview]
Message-ID: <4883867B.5000000@codemonkey.ws> (raw)
In-Reply-To: <fb249edb0807201007s177f8a18x30f19db4ab61080c@mail.gmail.com>

andrzej zaborowski wrote:
> 2008/7/20 Anthony Liguori <anthony@codemonkey.ws>:
>   
> With -no-graphic there's no ds->data, or it can have lower bpp than
> what's otherwise available.
>   

Screen dumping with -no-graphic probably should just show a black screen 
anyway.

I don't think a lower depth is really that big of a deal.  It's what the 
user would be seeing anyway.  The simplicity seems really nice to me.

>> I think your patch looks better, but I can also code up a new screen dumping
>> mechanism that doesn't take over DisplayState unless I'm missing something
>> obvious.
>>     
>
> It's worth a try, dumping ds->data is perhaps the way to go but
> ds->depth is being set to 32bit and various video cards are optimised
> on the assumption that ds->depth doesn't change, so maybe there should
> be a notification callback.
>   

Yeah, that's a bug BTW and AFAIK it's only a problem with VMware VGA.  
There's nothing that keeps ds->depth from changing after a screen resize 
with SDL.  If a VNC client does SetPixelFormat that will also change 
ds->depth.  Right now, some VNC clients + VMware VGA will cause a SEGV 
because of the assumptions that ds->depth doesn't change.

Regards,

Anthony Liguori

> Regards
>
>
>   

  reply	other threads:[~2008-07-20 18:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 21:19 [Qemu-devel] [PATCH 1/6] kvm: qemu: fix screendump with multiple consoles Anthony Liguori
2008-07-17 21:19 ` [Qemu-devel] [PATCH 2/6] kvm: qemu: force screen resize if a display buffer does not exist Anthony Liguori
2008-07-17 21:19 ` [Qemu-devel] [PATCH 3/6] kvm: qemu: revert "fix power management timer overflow handling" Anthony Liguori
2008-07-17 21:19 ` [Qemu-devel] [PATCH 4/6] kvm: qemu: revert ""QEMU keyboard issue with Gujin-2.2", by Etienne Lorrain." Anthony Liguori
2008-07-17 21:43   ` Even Rouault
2008-07-17 21:47   ` [Qemu-devel] " Jan Kiszka
2008-07-17 21:58     ` Anthony Liguori
2008-07-17 21:19 ` [Qemu-devel] [PATCH 5/6] kvm: qemu: improve scsi dma speed by increasing the dma buffer size Anthony Liguori
2008-07-20  2:37   ` Anthony Liguori
2008-07-17 21:19 ` [Qemu-devel] [PATCH 6/6] kvm: qemu: fix vga screendump Anthony Liguori
2008-07-19 14:36   ` andrzej zaborowski
2008-07-20  2:33     ` Anthony Liguori
2008-07-20 17:07       ` andrzej zaborowski
2008-07-20 18:39         ` Anthony Liguori [this message]
2008-07-20 19:28           ` andrzej zaborowski
2008-07-20 19:46             ` Anthony Liguori
2008-07-20 20:08               ` andrzej zaborowski
2008-07-20 21:53                 ` Anthony Liguori
2008-07-20 21:56                 ` Anthony Liguori
2008-07-21  2:00                   ` Jamie Lokier
2008-07-17 21:39 ` [Qemu-devel] [PATCH 0/6] Various fixes from KVM tree Anthony Liguori

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=4883867B.5000000@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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).