From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [RfC PATCH] virtio-pci: place msix regions in modern virtio bar
Date: Fri, 23 Jan 2015 17:12:24 +0200 [thread overview]
Message-ID: <20150123151224.GA6293@redhat.com> (raw)
In-Reply-To: <1422024508.13166.47.camel@nilsson.home.kraxel.org>
On Fri, Jan 23, 2015 at 03:48:28PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > > Also seabios wouldn't map the bar
> > > above 4G.
>
> > We can teach it to do that, and even if not, OS can do it on hotplug.
>
> Just to clarify: seabios can do it in the general case, it just wouldn't
> do it for xhci specifically because otherwise the seabios xhci driver
> wouldn't be able to reach the registers any more ...
>
> For non-transitional virtio-{blk,scsi,net} devices seabios (and ipxe)
> would have a simliar problem btw: When mapping the bars above 4G it
> can't handle the devices any more.
You can always use the config cap for this.
I didn't implement it yet, but I will.
> But we'll probably stick to transitional by default for a while (where
> seabios can just use the legacy registers in io address space),
io *is* very crowded. I think we should try and code up modern drivers
when we have the time.
> and
> there also is ovmf coming which runs in 64bit mode so mapping the bars
> high isn't a problem there.
>
> cheers,
> Gerd
>
prev parent reply other threads:[~2015-01-23 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 12:29 [Qemu-devel] [RfC PATCH] virtio-pci: place msix regions in modern virtio bar Gerd Hoffmann
2015-01-23 13:33 ` Michael S. Tsirkin
2015-01-23 13:53 ` Gerd Hoffmann
2015-01-23 13:58 ` Michael S. Tsirkin
2015-01-23 14:48 ` Gerd Hoffmann
2015-01-23 15:12 ` Michael S. Tsirkin [this message]
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=20150123151224.GA6293@redhat.com \
--to=mst@redhat.com \
--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 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).