xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Subject: [Fwd: Re: Wondering about cirris and stdvga]
Date: Fri, 18 Nov 2016 22:57:44 +0100	[thread overview]
Message-ID: <1479506264.3832.72.camel@citrix.com> (raw)
In-Reply-To: 1479500348.16973.1.camel@redhat.com

-------- Forwarded Message --------
From: Adam Jackson <ajax@redhat.com>
Subject: Re: Wondering about cirris and stdvga
Date: Fri, 18 Nov 2016 15:19:08 -0500
Message-Id: <1479500348.16973.1.camel@redhat.com>

On Fri, 2016-11-18 at 13:32 -0500, Konrad Rzeszutek Wilk wrote:
> 
> On Fri, Nov 18, 2016 at 06:08:57PM +0000, Ian Jackson wrote:
> > 
> > 
> > > 
> > > performance wise, that cirrus is broken and impossible to
> > > fix (because it is the hardware that it's emulating that was
> > > broken),
> > > that stdvga enables better screen resolution in guests, etc.
> > 
> > The "broken and impossible to fix" sounds like FUD TBH.

The "fear" bit, perhaps; it is arguably frightening that we continue to
emulate in 2016 a chip that was inadequate in 1996. In my opinion about
cirrus being broken, however, I am neither uncertain nor in doubt.

> 
> > 
> > I wouldn't want to change the default just because Wayland is
> > broken.
> > Wayland should be fixed.

You should want to change the default because it is bad, even for X.

> 
> CCing Adam Jackson who I hope can enlighten us on the technical
> parts of Xorg.
> 
> I am really interested in knowing the technical merits
> of the stdvga vs cirrus and I hope to understand what the Xorg
> maintainer(s) have in mind.

The cirrus chip that qemu happens to emulate is trash. It can't do
32bpp, it can't do modes larger than 2048 wide, it can't do more than
4M of VRAM. We could of course extend the qemu emulation to be more
capable; doing so would require updating every guest to know about
these enhancements, though.

stdvga, as it has none of the above problems, is _today_ uniformly
better than cirrus. It is still perhaps less awesome than one would
like (no idea how multihead is expected to work for example), but there
is no world in which stdvga is worse than cirrus.

- ajax
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

       reply	other threads:[~2016-11-18 21:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1479500348.16973.1.camel@redhat.com>
2016-11-18 21:57 ` Dario Faggioli [this message]
2016-11-18 22:31   ` [Fwd: Re: Wondering about cirris and stdvga] Dario Faggioli
     [not found] <1479500639.16973.3.camel@redhat.com>
2016-11-18 21:57 ` Dario Faggioli
     [not found] <alpine.DEB.2.10.1611181123310.3290@sstabellini-ThinkPad-X260>
2016-11-18 21:57 ` Dario Faggioli
     [not found] <20161118183224.GB10560@x230.dumpdata.com>
2016-11-18 21:57 ` Dario Faggioli
     [not found] <22575.17337.627347.934459@mariner.uk.xensource.com>
2016-11-18 21:57 ` Dario Faggioli

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=1479506264.3832.72.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=xen-devel@lists.xenproject.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).