From: Isaku Yamahata <yamahata@valinux.co.jp>
To: Alexey Korolev <alexey.korolev@endace.com>
Cc: Stephen Donnelly <Stephen.Donnelly@endace.com>,
seabios <seabios@seabios.org>,
qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] [Seabios] Over 4GB address ranges for 64bit PCI BARs
Date: Mon, 8 Nov 2010 13:11:02 +0900 [thread overview]
Message-ID: <20101108041102.GM26077@valinux.co.jp> (raw)
In-Reply-To: <1289187338.28768.120.camel@nzhmlwks0057>
On Mon, Nov 08, 2010 at 04:35:38PM +1300, Alexey Korolev wrote:
> > - >4GB 64bit bar allocation
> > Your patche tries to address this issue. But it breaks PCI-to-PCI
> > bridge filtering support.
> Hmm, it is quite possible, as we don't know a lot about seabios PCI-to-PCI bridge filtering support.
> Just out of curiosity: what is the issue?
It's pci_bios_init_device_bridge() in pciinit.c.
The function touches pci_bios_io_addr, pci_bios_mem_addr, and
pci_bios_prefmem_addr.
So we need to modify, not only pci_bios_allocate_region(),
but also pci_bios_init_device_bridge().
The function programs the P2P bridge to forward IO/memory access
on primary pci bus to secondary pci bus.
It needs to be aware of 64bit BAR allocation.
> > If the BAR size is huge (or there are too many BARs), the bar can't
> > be allocated under 4G. So several persons want seabios to allocate
> > such BARs at >4GB area complaining that OS can't use BARs that seabios
> > didn't assigned.
> >
> > Others think such BAR can be left unallocated.
> > Seabios role is to setup minimal basic environment for bootloader
> > to boot OS, 64bit bar allocation is beyond it's role.
> > bootloader/rombios usually doesn't handle BARs that is allocated
> > beyond 4GB, and Modern OSes can re-arrange PCI bar allocation itself.
> > So 64bit bar allocation support wouldn't be needed.
> >
> > I'm not sure if there is enough demand to support 64bit BAR allocation
> > and if Kevin will accept it or not. Consensus is needed.
> > What OS are you using?
> >
> For us >4GB allocation is welcome but not critical, because we mainly
> use Linux versions 2.6.18 and newer. We've tested the seabios without
> assignment of the regions which do not fit in first 32bit and it appears
> to work fine. So for us 64bit bar allocation support wouldn't be needed.
>
> It is possible that people will use an ancient version of Linux, but the
> probability of this event is very low.
My position is same to yours. Welcome, but not critical.
So the issue is, who will finish it.
--
yamahata
prev parent reply other threads:[~2010-11-08 4:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 2:13 [Qemu-devel] [PATCH] [Seabios] Over 4GB address ranges for 64bit PCI BARs Alexey Korolev
2010-11-05 4:16 ` [Qemu-devel] " Isaku Yamahata
2010-11-08 3:35 ` Alexey Korolev
2010-11-08 4:11 ` Isaku Yamahata [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=20101108041102.GM26077@valinux.co.jp \
--to=yamahata@valinux.co.jp \
--cc=Stephen.Donnelly@endace.com \
--cc=alexey.korolev@endace.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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).