All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@kernel.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH] virtio-pci: make pci bar layout more flexible.
Date: Wed, 4 Mar 2015 12:04:44 +0100	[thread overview]
Message-ID: <20150304110444.GB27463@redhat.com> (raw)
In-Reply-To: <1425466550.8389.10.camel@nilsson.home.kraxel.org>

On Wed, Mar 04, 2015 at 11:55:50AM +0100, Gerd Hoffmann wrote:
>   Hi,
> 
> > > VirtIOPCIProxy subclasses which need additional pci bars, such as
> > > virtio-vga, just need to make sure they register the additinal bars
> > > before initializing virtio-pci, so the superclass can see the registered
> > > bars and shuffle around the virtio bars accordingly.
> > 
> > I think I prefer we just DTRT and keep same layouts for everyone by
> > default: isn't there a layout that is good for everybody?
> 
> I want bar #2 for the vga framebuffer for virtio-vga.  Which conflicts
> with bar #2 being used for the modern bar in todays code.

OK, and IIUC you are saying that using bar #2 for that is a requirement for
vga to work?

> We can move the modern bar to #4 for everybody, then we'll have:
> 
>   #0 -- legacy i/o
>   #1 -- msix
>   #2 -- unused (by virtio)
>   #3 -- unused (by virtio)
>   #4 -- modern mem
>   #5 -- modern mem too (because it's 64bit).
> 
> That'll leave bars #2 + #3 free, for additional bars (1x 64bit or 2x
> 32bit) such as vga framebuffer if needed.

Yes, that's fine with me.

> > I know this means we'll leave BAR0 unused for modern devices but that
> > does not seem too bad.
> 
> Yep, no technical reason against it, although it IMHO looks nicer.
> 
> cheers,
>   Gerd

If we run into a problem, we'll be able to reshuffle it all easily.

-- 
MST

  reply	other threads:[~2015-03-04 11:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 13:55 [Qemu-devel] [PATCH] virtio-pci: make pci bar layout more flexible Gerd Hoffmann
2015-03-03 17:42 ` Michael S. Tsirkin
2015-03-04 10:55   ` Gerd Hoffmann
2015-03-04 11:04     ` Michael S. Tsirkin [this message]
2015-03-04 11:46       ` Gerd Hoffmann
2015-03-04 11:51         ` Michael S. Tsirkin
2015-03-04 12:04           ` Michael S. Tsirkin

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=20150304110444.GB27463@redhat.com \
    --to=mst@kernel.org \
    --cc=aliguori@amazon.com \
    --cc=kraxel@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 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.