qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] vga-pci and MMIO BAR
Date: Wed, 25 Jul 2012 20:53:38 +1000	[thread overview]
Message-ID: <1343213618.3715.48.camel@pasglop> (raw)
In-Reply-To: <500FC9F8.6010002@redhat.com>

On Wed, 2012-07-25 at 13:27 +0300, Avi Kivity wrote:
> On 07/25/2012 06:57 AM, Benjamin Herrenschmidt wrote:
> > Hi folks !
> > 
> > Would there be any objection to adding a second MMIO BAR to qemu-vga
> > which mirrors the bochs magic VBE ports ?
> > 
> > Support for IO space is optional in PCIe and can be problematic on some
> > architectures, it would be nice to be able to program the card entirely
> > using mmio.
> 
> Can we choose a PCIe chipset that does support IO space?

Why bother ? It's not like mode setting is performance critical and IO
space is always going to be a pain on non-x86 ...

> If not, we can add a second BAR, but it should disappear when running an
> older machine type.

Well, the IO ports in legacy space are still there. We can also make the
"register BAR" exist in both mode or we can add a second BAR and have
x86 "prefer" IO... whatever rocks your boat as long as it's a BAR, it's
the legacy hole that's annoying for me :-)

> > Once done, I'd like to look into doing a qemudrmfb similar to the cirrus
> > one that pretty much gives you generic KMS support (with RandR) on top
> > of vga-pci. This would have the advantage of potentially lifting the
> > pitch and size limitations that plague cirrus.
> 
> Have a look at qxl.

No I haven't :-) I'll have a look, thanks.

Cheers,
Ben.

  reply	other threads:[~2012-07-25 10:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-25  3:57 [Qemu-devel] vga-pci and MMIO BAR Benjamin Herrenschmidt
2012-07-25 10:27 ` Avi Kivity
2012-07-25 10:53   ` Benjamin Herrenschmidt [this message]
2012-07-25 12:48     ` Avi Kivity
2012-07-25 13:41       ` Benjamin Herrenschmidt
2012-07-25 13:59         ` Avi Kivity
2012-07-25 22:01           ` Benjamin Herrenschmidt
2012-07-26  0:22             ` Benjamin Herrenschmidt
2012-07-26  1:08               ` Anthony Liguori
2012-07-26  1:18                 ` Benjamin Herrenschmidt
2012-08-06 12:03 ` Gerd Hoffmann
2012-08-06 21:07   ` Benjamin Herrenschmidt
2012-08-10 15:27   ` Alon Levy

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=1343213618.3715.48.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=avi@redhat.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).