From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCH] x86: use 'dom0_mem' to limit the number of pages for dom0 Date: Tue, 16 Aug 2011 14:11:47 +0100 Message-ID: <4E4A6C93.10008@citrix.com> References: <1ec6c392d40f37032b0c.1313431713@qabil> <20110816003158.GA26540@dumpdata.com> <4E4A62B9.4030302@citrix.com> <1313499116.5010.104.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1313499116.5010.104.camel@zakaz.uk.xensource.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: Ian Campbell Cc: "xen-devel@lists.xensource.com" , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On 16/08/11 13:51, Ian Campbell wrote: > > The key difference is that classic-Xen kernels called both > XENMEM_memory_map and XENMEM_machine_memory_map and dealt with both, > whereas pvops (dom0) calls XENMEM_machine_memory_map and tries to figure > out how much of the E820_RAM therein it can actually use based on > nr_pages and such. You've used XENMEM_maximum_reservation in your > followup series which I think is a suitable surrogate for calling > XENMEM_memory_map (although I didn't check). XENMEM_memory_map for dom0 doesn't work as nothing populates the map. Classic-Xen kernels appear to invent a memory map based only on nr_pages and it's non-obvious where it gets any other limit from (I didn't look that hard though). I did originally make XENMEM_memory_map work for dom0 but using XENMEM_maximum_reservation looked more relevant. David