From: Keir Fraser Subject: Re: [RFC Patch] Support for making an E820 PCI hole in toolstack (xl + xm) Date: Mon, 15 Nov 2010 18:41:16 +0000 Message-ID: References: <20101115181544.GA8840@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20101115181544.GA8840@dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: Jeremy Fitzhardinge , xen-devel@lists.xensource.com, bruce.edge@gmail.com, gianni.tedesco@citrix.com, stefano.stabellini@eu.citrix.com List-Id: xen-devel@lists.xenproject.org On 15/11/2010 18:15, "Konrad Rzeszutek Wilk" wrote: >> Well it is all quite Xen specific, so I'm surprised. > > Oh, there was another reason that I so obvious that I completly forgot. DomU > has no idea where the host PCI hole starts. In most cases it is at 3GB (or > even > further up - 3.5GB), but a quick look for 'Allocating PCI resources starting > at' > at Google shows that there are some that start at 1.2G. Hm, true. We could give you access to XENMEM_machine_memory_map? It's not really got any big secrets or privileged things in it. :-) Or, is there much disadvantage, to having a static really big PCI hole? Say starting at 1GB? The advantage of this would be the ability to hotplug PCI devices to a domU even across save/restore/migrate -- this may not work so well if you commit yourself to the hole size of the original host, and the restore/migrate target host has a bigger hole! -- Keir