qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 3/3] Changes related to secondary buses and 64bi


From: Kevin O'Connor
Subject: Re: [Qemu-devel] [PATCH 3/3] Changes related to secondary buses and 64bit regions
Date: Fri, 30 Dec 2011 01:02:16 -0500
User-agent: Mutt/1.5.21 (2010-09-15)

On Fri, Dec 30, 2011 at 06:10:13PM +1300, Alexey Korolev wrote:
> On 30/12/11 05:21, Michael S. Tsirkin wrote:
> >On Thu, Dec 29, 2011 at 06:41:36PM +1300, Alexey Korolev wrote:
> >>>Can't figure this out. What does this do?
> >>Bios will panic if it founds prefmem BARs in both 32bit and 64bit areas.
> >That's not good, it's a legal configuration.
> >
> To be more complete : Bios will panic if it founds prefmem BARs in
> both 32bit and 64bit areas
> on the same secondary Bus.
> I agree about that this limitation is too strict at the moment. But
> this is just a limitation, there are
> plenty of them in Seabios.

There are very few panic calls in seabios.  Halting in the system
firmware is very unfriendly and should be avoided.

As described in my other email, if there is a mix of prefmem bars on a
secondary bus, then just allocate all those bars in the first 4gig.
No reason to halt the boot.

> To answer if it is a legal or not we need to have a look how real
> BIOS would behave in a such
> scenario. Unfortunately I have no chance to have this configuration
> on hand. If you have (may
> have) this I would appreciate if you let us know how the Bios will behave?

You can look at the pci allocation code in coreboot.

-Kevin



reply via email to

[Prev in Thread] Current Thread [Next in Thread]