qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Michael S. Tsirkin" <mst@kernel.org>,
	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:51:35 +0100	[thread overview]
Message-ID: <20150304115135.GB28099@redhat.com> (raw)
In-Reply-To: <1425469610.8389.29.camel@nilsson.home.kraxel.org>

On Wed, Mar 04, 2015 at 12:46:50PM +0100, Gerd Hoffmann wrote:
> On Mi, 2015-03-04 at 12:04 +0100, Michael S. Tsirkin wrote:
> > 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?
> 
> Makes things alot easier as seavgabios has support for virtio-vga (in
> vga compat mode) already and expects the framebuffer being in bar #2.
> 
> It's not a _really_ hard requirement though.
> 
> cheers,
>   Gerd
> 

Easy is good, I think we don't really care where the modern bar is,
let's just move it for everyone, and add a comment explaining the
motivation.

-- 
MST

  reply	other threads:[~2015-03-04 11:51 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
2015-03-04 11:46       ` Gerd Hoffmann
2015-03-04 11:51         ` Michael S. Tsirkin [this message]
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=20150304115135.GB28099@redhat.com \
    --to=mst@redhat.com \
    --cc=aliguori@amazon.com \
    --cc=kraxel@redhat.com \
    --cc=mst@kernel.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 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).