qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] DisplayState interface change


From: Stefano Stabellini
Subject: Re: [Qemu-devel] [PATCH] DisplayState interface change
Date: Mon, 17 Nov 2008 16:07:48 +0000
User-agent: Thunderbird 2.0.0.14 (X11/20080505)

Anthony Liguori wrote:

> If we're going to change DisplayState, and I think it's long over due
> that we do, then I think we should try to make sure we get it right.
> 
> What I would like to see is the buffer information extracted into a
> separate structure.  That buffer should also describe the pixel format
> in a much more thorough way.  There should be, in the very least, an
> endianness flag, information about the per-color shift and per-color
> mask, the bits per pixel, the bytes per pixel, the width and the height.


That should be pretty easy to do, since we already have all those
informations.


> We should also have generic conversion functions to convert from one
> buffer to another.  This would allow us to simplify a lot of things
> (like screen shot).  It also ties in better to other display tool kits. 
> Right now we have too many assumptions about what the pixel layout is
> from the depth.


Those functions right now are in vga_template.h I tried not to change it
in this patch.

> The other thing to consider is that we do need some level of
> bidirectional communication.  vmware VGA supports the ability to tell
> the guest what resolution/depth it ought to be using.  You really want
> to get that information from SDL (at least the depth bits) so that we
> can avoid blitting.  With KVM, we can pretty trivially directly map the
> SDL buffer directly into the guest's physical memory provided it uses
> the right format.
> 


I agree that it be nice, we could probably do something like that on
xen too.

Please don't ask me to make these big changes (generic functions,
bidirectional communication) on top of this patch in order for it to get
applied.
This patch is already too long, it would be difficult to
accomplish all the things you suggested in a single shot without
breaking anything.
I think it is best to do this incrementally and work together on the
features suggested after this patch gets applied.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]