qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3 of 6] vga shared buffer
Date: Wed, 24 Sep 2008 11:53:31 +0100	[thread overview]
Message-ID: <48DA1C2B.9030303@eu.citrix.com> (raw)
In-Reply-To: <fb249edb0809232000u6b0d7e97na20f6c937fb7c7ac@mail.gmail.com>

andrzej zaborowski wrote:

> 2008/9/15 Anthony Liguori <anthony@codemonkey.ws>:
>> Stefano Stabellini wrote:
>>> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>>>
>> I need to carve out some time to test this series and think about whether it
>> can be done without adding a new DisplayState hook.  I should be able to
>> respond or apply within a few days.
> 
> Any news? I think this change makes sense and it can help remove the
> DIRECT_VRAM hack from vmware_vga.c.


Thanks for keeping this thread alive.
I was fearing it was slowing slipping into oblivion.

 
>> I'm concerned about the complexity this adds to back-ends.  It's not clear
>> to me whether the performance justifies the added complexity.
> 
> One way to simplify this and everything else is use Stefano's code to
> stop the backends (SDL, VNC) from managing the framebuffer altogether
> and only support what these patches call shared buffer.  Then if the
> given backed doesn't support given colorspace conversion in hardware,
> it's its call to implement this, it could unify the color conversion
> in qemu more generally.  The drawback is it's hard to support weird
> colorspaces like those supported by OMAP2 display susbsystem, and even
> harder to do features like overlaid framebuffers with different
> colorspaces (but it's not currently implemented anyway).
> 

I wouldn't be so concerned about complexity: backends can always drop
completely any shared buffer related code and still work fine.
The vga code instead is not changed much (sadly I had to move some code
around but the real changes are really few, about 20 lines of code, I
would say).

I am not sure to understand correctly what you are suggesting, are you
proposing to always share the buffer and leave completely any color
conversion to the backends?

If so, that would simplify the code changes in vga.c, but not by much
(keep in mind that we would still need to move the code I am moving
right now, so we would only affect the remaing ~20 lines added).
It would leave sdl mostly unaffected, because with my patches it already
does all the color conversions itself.
Finally it would add complexity to vnc.c, that at the moment is only
able to handle 16 bpp.

      parent reply	other threads:[~2008-09-24 10:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12 11:26 [Qemu-devel] [PATCH 3 of 6] vga shared buffer Stefano Stabellini
2008-09-15 16:06 ` Anthony Liguori
2008-09-15 16:47   ` Stefano Stabellini
2008-09-24  3:00   ` andrzej zaborowski
2008-09-24  3:25     ` Anthony Liguori
2008-09-24 10:53     ` Stefano Stabellini [this message]

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=48DA1C2B.9030303@eu.citrix.com \
    --to=stefano.stabellini@eu.citrix.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).