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/
Home Products Support Community News


[Patch] was Re: [Xen-ia64-devel] Good projects for someone

To: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Patch] was Re: [Xen-ia64-devel] Good projects for someone
From: Tristan Gingold <Tristan.Gingold@xxxxxxxx>
Date: Tue, 3 Jan 2006 17:08:43 +0100
Delivery-date: Tue, 03 Jan 2006 15:10:21 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200601031212.10169.Tristan.Gingold@xxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <516F50407E01324991DD6D07B0531AD5902B42@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <200601031212.10169.Tristan.Gingold@xxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.5
Le Mardi 03 Janvier 2006 12:12, Tristan Gingold a écrit :
> Le Jeudi 22 Décembre 2005 19:33, Magenheimer, Dan (HP Labs Fort Collins) a
> écrit :
> > 1) While working on the domU fix earlier in the week, I
> > discovered that Xen/ia64 still ignores any machine memory
> > at an address > 4GB (see xen/arch/ia64/linux-xen/efi.c and
> > search for "hack").  I think nearly all Itanium machines
> > leave some portion of 1GB-4GB unpopulated so most memory
> > is getting wasted!  I think CONFIG_VIRTUAL_MEM_MAP needs
> > to be implemented to fix this.  (Removing the hack causes
> > a "Not enough memory for frametable" panic.)

I tried to remove the hack, but I got only a fatal error when dom0 was built.
Here is a patch which fixes the issue: dom0 image was not correctly protected
from memory allocator.

I also remove the hack since it seems to work.  My machine has 8GB.  The 
frame_table uses about 55MB (72 bytes per page)!

I am not sure we need a virtual memmap, if I understand correctly what it is.
The current approach simply wastes many memory in unused frame_table entries.


Signed-off-by: Tristan Gingold <tristan.gingold@xxxxxxxx>

Attachment: xen-4gb.diffs
Description: Text Data

Xen-ia64-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>