Re: [Xen-devel] Xen 4.3 development update

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Tue, 2013-06-11 at 14:53 +0100, Stefano Stabellini wrote:
> On Tue, 11 Jun 2013, George Dunlap wrote:
> > On Mon, Jun 10, 2013 at 5:04 PM, George Dunlap
> > <George.Dunlap@xxxxxxxxxxxxx> wrote:
> > > * qemu-upstream MMIO hole issue
> > >  > http://lists.xen.org/archives/html/xen-devel/2013-03/msg00559.html
> > >  > "You can reproduce it when a VM has a big pci hole size (such as
> > >    512MB), e.g. create a VM with a virtual device which has a 512MB
> > >    pci BAR."
> > >  priority: high
> > >  status: Original fix broken; investigating proper fix
> > >  priority: blocker (?)
> > 
> > Any chance someone could spend a bit of time digging into SeaBIOS /
> > qemu to see if:
> > 1. SeaBIOS has any logic for querying the PCI space and changing the
> > size of the PCI hole
> > 2. If SeaBIOS can do this when running on qemu, and if so, why it's not 
> > working?
> 
> AFAICT SeaBIOS is going to use the address space between
> BUILD_PCIMEM_START (0xe0000000) and BUILD_PCIMEM_END (0xfec00000) as PCI
> hole, when it runs out, it is going to return error.
> 
> See src/pciinit.c:pci_setup

Which starts with:

    if (CONFIG_COREBOOT || usingXen()) {
        // PCI setup already done by coreboot or Xen - just do probe.
        pci_probe_devices();
        return;
    }

So doesn't apply to our case (or the native hardware case)

Ian.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel