All of lore.kernel.org
 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:32 +0100	[thread overview]
Message-ID: <1479506252.3832.71.camel@citrix.com> (raw)
In-Reply-To: alpine.DEB.2.10.1611181123310.3290@sstabellini-ThinkPad-X260

-------- Forwarded Message --------
From: Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: Wondering about cirris and stdvga
Date: Fri, 18 Nov 2016 11:26:07 -0800
Mailer: Alpine 2.10 (DEB 1266 2009-07-14)
Message-Id: <alpine.DEB.2.10.1611181123310.3290@sstabellini-ThinkPad-
X260>

On Fri, 18 Nov 2016, Konrad Rzeszutek Wilk wrote:
> 
> On Fri, Nov 18, 2016 at 06:08:57PM +0000, Ian Jackson wrote:
> > 
> > Dario Faggioli writes ("Wondering about cirris and stdvga"):
> > > 
> > > I've also read around that these days, e.g., stdvga is at least
> > > as good
> > > as cirrus,
> > 
> > You pasted a url in IRC which seemed to be arguing that but
> > actually
> > failed to make the case.  (Sorry, don't have it to hand now.)
> 
> This one?
> https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harm
> ful/
> > 
> > 
> > > 
> > > 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.
> > 
> > I wouldn't want to change the default just because Wayland is
> > broken.
> > Wayland should be fixed.
> 
> 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.
 
I am no Xorg maintainer but back in the XenClient days we did some perf
analysis and it turned out that the bitblt operations supported by
Cirrus are actually very slow to emulate in QEMU. stdvga is faster
because it doesn't support them. In addition stdvga supports higher
resolutions: as high as the videoram assigned to the guest can support,
while cirrus is limited.
-- 
<<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] <alpine.DEB.2.10.1611181123310.3290@sstabellini-ThinkPad-X260>
2016-11-18 21:57 ` Dario Faggioli [this message]
     [not found] <1479500639.16973.3.camel@redhat.com>
2016-11-18 21:57 ` [Fwd: Re: Wondering about cirris and stdvga] Dario Faggioli
     [not found] <1479500348.16973.1.camel@redhat.com>
2016-11-18 21:57 ` Dario Faggioli
2016-11-18 22:31   ` 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=1479506252.3832.71.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.