From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: [edk2] Passing Xen memory map and resource map to OVMF Date: Thu, 14 Nov 2013 08:58:18 +0100 Message-ID: <1384415898.15534.15.camel__18890.2029338808$1384416029$gmane$org@nilsson.home.kraxel.org> References: <20131112183321.GN13369@zion.uk.xensource.com> <52827C0B.5040901@redhat.com> <1384326219.3560.9.camel@nilsson.home.kraxel.org> <20131113115811.GC4948@zion.uk.xensource.com> <1384350814.3560.24.camel@nilsson.home.kraxel.org> <20131113140654.GF4948@zion.uk.xensource.com> <1384352585.3560.36.camel@nilsson.home.kraxel.org> <20131113165644.GA16969@zion.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20131113165644.GA16969@zion.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu Cc: "Jordan Justen (Intel address)" , Igor Mammedov , edk2-devel@lists.sourceforge.net, Laszlo Ersek , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org Hi, > > > 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. cheers, Gerd