qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] Cirrus bugs vs endian: how two bugs cancel each other o


From: Avi Kivity
Subject: Re: [Qemu-devel] Cirrus bugs vs endian: how two bugs cancel each other out
Date: Mon, 30 Jul 2012 15:15:37 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1

On 07/30/2012 03:08 PM, Benjamin Herrenschmidt wrote:
> On Mon, 2012-07-30 at 14:58 +0300, Avi Kivity wrote:
>> Let's balkanize some more then?
>> 
>> No, qxl is our paravirt vga, we should improve it instead of spawning
>> new ones (which will be horrible in the eyes of the next person to look
>> at them).  You should also be getting the drm driver for free.
>> 
>> http://spice-space.org/page/DRM
> 
> "Free" is a big word here, I wouldn't be surprised if it was totally
> endian busted :-)

Probably... well fixing endianness is the price of doing business if
you're big endian.

> 
> Why so much effort into a bad design on top of a crack transport btw ?
> Is it just RH politics of there's a good reason hiding somewhere ? Some
> kind of morbid fascination for anything Windows ?

It was indeed designed for Windows, which is the prime target for
desktop virtualization.  As to the rest, I don't know much about it,
except that no politicians were involved in the design.

> 
> People I've talked to around in the community seem to agree that some
> minor improvements on qemu-vga are worthwhile, so I'm doing them,
> nothing drastic, mostly having a mirror of the legacy IO registers in an
> MMIO BAR so it's more usable for non-x86 platforms, and I'm about to add
> some simplistic 2D blit facility so we can have a semi-decent fb console
> over vnc. I can trivially do an equivalent of cirrusdrmfb for it so we
> get X mode setting / RandR.
> 
> That gives us a baseline for mostly unaccelerated 2D.

That's fine.

> Something tells me that getting that spice/qxl gunk will be more than a
> trivial effort (but I might be wrong) and I'm reluctant to start
> committing effort on it since so far I yet have to see it being actually
> picked up by people.

I think it's prudent to wait until it's merged upstream, then we can
take another look to see why ppc is so special that it can't just use it
after fixing any endianness issues.

-- 
error compiling committee.c: too many arguments to function





reply via email to

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