WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] bring up Hypervisor on large (512GB) memory

To: "mukesh.rathor@xxxxxxxxxx" <mukesh.rathor@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] bring up Hypervisor on large (512GB) memory
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 10 Feb 2009 05:34:28 +0000
Cc:
Delivery-date: Mon, 09 Feb 2009 21:35:00 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4990EFC7.9000907@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcmLLQBsmLYmXXNlRISVPSwP3zg14QAFD02A
Thread-topic: [Xen-devel] bring up Hypervisor on large (512GB) memory
User-agent: Microsoft-Entourage/12.15.0.081119
On 10/02/2009 03:08, "Mukesh Rathor" <mukesh.rathor@xxxxxxxxxx> wrote:

> The only solution I can think of is moving the bitmap elsewhere, above 4GB in
> this case:
>     figure the size of bitmap, DIRECT map space, allocate the map,
>     mark it reserved in the RAM map, and should work!
> 
>     I'd have add a loop around init_boot_allocator() in __start_xen()
>     iterating thru the RAM map again, and finding space above 16M.
> 
> Am I on the right track?

A 512GB system still needs only 16MB of allocator bitmap. There's no need
for a complicated solution, moving it above 4GB or anything.

I've actually broken xen-unstable and forgotten to account for the allocator
bitmap overhead when I relocate Xen. I will fix that, and properly account
for the bitmap overhead rather than add a fixed overhead (which is probably
what breaks you on 3.1.4). I'll let you know when that's done.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel