From: Benjamin Herrenschmidt <benh@au1.ibm.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: "Alexander Graf" <agraf@suse.de>,
"Li Zhang" <zhlcindy@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, "Li Zhang" <zhlcindy@gmail.com>,
qemu-ppc <qemu-ppc@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>,
mjg@redhat.com
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 2/2] spapr: Add support for -vga option
Date: Mon, 23 Jul 2012 16:40:21 +1000 [thread overview]
Message-ID: <1343025621.2957.27.camel@pasglop> (raw)
In-Reply-To: <4FEB886A.5000605@us.ibm.com>
On Wed, 2012-06-27 at 17:25 -0500, Anthony Liguori wrote:
> If a user asks for something and we can't make it work, we should fail.
Note that QEMU's cirrus works fine with the new kernel cirrusdrmfb, so
I say we should allow it (needs to be able to the powerpc device .mak
as well tho.
It shouldn't be primary because old RHEL's iirc used to have cirrusfb
enabled and that would blow due to guest kernel bugs among others.
I haven't had a chance to try whatever userspace DDX the Xorg folks have
come up with to use on top of cirrusdrmfb, so that might need a bit of
fixing but there's no reason not to allow -vga cirrus at this point.
Note to Matthew: cirrusdrmfb is a LOT SLOWER than offb for a similar
SW only dumb framebuffer, probably has to do with the way it does the
"dirty" stuff, not sure ...
Why not draw directly into the emulated vram ?
Cheers,
Ben.
next prev parent reply other threads:[~2012-07-23 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 9:34 [Qemu-devel] [PATCH 2/2] spapr: Add support for -vga option Li Zhang
[not found] ` <80058105-0CF7-4FBD-BD4A-EF7532A8F5B8@suse.de>
[not found] ` <1340833174.3732.65.camel@pasglop>
[not found] ` <9D81F5FD-C680-4CC4-B3E0-E737C84BC1DB@suse.de>
[not found] ` <1340834707.3732.81.camel@pasglop>
[not found] ` <92004E32-9F3E-4F4F-8287-B2EF25C7B4F9@suse.de>
[not found] ` <4FEB886A.5000605@us.ibm.com>
2012-07-23 6:40 ` Benjamin Herrenschmidt [this message]
2012-07-23 7:27 ` [Qemu-devel] [Qemu-ppc] " Benjamin Herrenschmidt
2012-07-23 13:24 ` Matthew Garrett
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=1343025621.2957.27.camel@pasglop \
--to=benh@au1.ibm.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=mjg@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=zhlcindy@gmail.com \
--cc=zhlcindy@linux.vnet.ibm.com \
/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).