All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] vga-pci and MMIO BAR
Date: Wed, 25 Jul 2012 15:48:07 +0300	[thread overview]
Message-ID: <500FEB07.5010009@redhat.com> (raw)
In-Reply-To: <1343213618.3715.48.camel@pasglop>

On 07/25/2012 01:53 PM, Benjamin Herrenschmidt wrote:
> 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 ...

For compatibility?  If it's a special pain, then I understand, but
what's the difference between emulating chipset A or B?

> 
>> 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 :-)

A guest created with -M old must look exactly the same as it did in an
older version of qemu, no extra BARs.


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

  reply	other threads:[~2012-07-25 12:48 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
2012-07-25 12:48     ` Avi Kivity [this message]
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=500FEB07.5010009@redhat.com \
    --to=avi@redhat.com \
    --cc=benh@kernel.crashing.org \
    --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 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.