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

Re: [Xen-devel] [edk2] Passing Xen memory map and resource map to OVMF


> > > OVMF
> > > should just use whatever it gets.
> > 
> > What would OVMF use them for?
> > 
> To reserve range for MMIO holes, so that later PCI resource allocation
> protocol can only use those ranges.

I'm still not convinced you need that in the first place.

When booting seabios @ xen it is not needed.  pci ressource allocation
is handled by hvmloader.  apci tables (and the ressources declared
therein) are handled by hvmloader.  seabios doesn't touch the pci bars
and passes through the apci tables -> guest os is happy.

So why ovmf should be different?   IMHO it should operate like seabios
and NOT do pci ressource allocation when running on xen.  Ressources are
already handled already by hvmloader.  Doing it again is (a) pointless
and (b) creates problems like the one we are discussion right now.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.