From: Keir Fraser Subject: Re: [PATCH]: Allow Xen to boot/run on large memory (>64G) machines Date: Thu, 22 Feb 2007 15:11:50 +0000 Message-ID: References: <45DDAF46.60404@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <45DDAF46.60404@redhat.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: Chris Lalancette Cc: xen-devel@lists.xensource.com, Jan Beulich List-Id: xen-devel@lists.xenproject.org On 22/2/07 14:57, "Chris Lalancette" wrote: >> It makes sense for the boot allocator to prefer to allocate from high memory >> if it can, rather then using what is currently the DMA pool (and, after your >> patches are applied, will be from relatively-narrow-address-width pools). So >> I think this patch is good and narrow enough in scope to go straight in >> (although I think the behaviour of alloc_boot_pages() should be changed >> rather than adding a new allocator function). > > Yeah, I wasn't quite sure how far to go with this. The frame table was the > worst offender, so I just went after that. I can whip up a quick patch and > test > it out here, changing the alloc_boot_pages() to always allocate from the top. Turns out there is one place that wants to allocate from the bottom (the kdump path in arch/x86/setup.c). So I renamed alloc_boot_pages() to alloc_lowmem_boot_pages() and called the new function alloc_boot_pages(). If you care you use the more specific (lowmem) one. I'm about to check in the revised patch. > By the way, I assume we only want to do this for x86_64, yes? No, it makes sense to conserve 'narrower' addresses. -- Keir