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

Re: [Xen-devel] [PATCH]: Allow Xen to boot/run on large memory (>64G) machines

  • To: Chris Lalancette <clalance@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Thu, 22 Feb 2007 07:50:04 +0000
  • Delivery-date: Wed, 21 Feb 2007 23:49:23 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdWVhAPTrYcR8JJEduXfgAWy6hiGQ==
  • Thread-topic: [Xen-devel] [PATCH]: Allow Xen to boot/run on large memory (>64G) machines

On 22/2/07 00:38, "Chris Lalancette" <clalance@xxxxxxxxxx> wrote:

>      Note that this is not the end of the story, however.  For even larger
> machines, it can *still* be the case that the allocation in construct_dom0()
> fails; in particular, if the order goes above 17, it will fail in the same
> way.
>  One way to fix it would be to just allocate that memory out of the normal
> zone
> for x86_64, as well; however, I'm not sure if this will break anything else.
> Any comments?

If there are no users of alloc_boot_pages() expecting low memory to be
returned then we can adjust the implementation of that existing function
rather than introduce a new one.

As for domain_build() there are two considerations: firstly that the
allocation is contiguous and secondly that it is from the DMA pool. The
builder makes simplifying assumptions based on contiguity. The allocation
from DMA pool I think I've tried to get rid of before -- I think I was
scuppered by something as simple as the PAE pgdir needing to be allocated
from low memory. I think we can stop allocating from the DMA pool, at least
for non-PAE host.

 -- Keir

Xen-devel mailing list



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