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

[Xen-devel] [PATCH] [RFC] Moving the e820 table creation

To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, keir.fraser@xxxxxxxxxxxx
Subject: [Xen-devel] [PATCH] [RFC] Moving the e820 table creation
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Mon, 06 Nov 2006 15:06:41 -0500
Delivery-date: Mon, 06 Nov 2006 12:08:00 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
This patch tries to move the e820 table creation out of libxc into the
hvmloader in order to properly account for the ACPI space using the
#defines for the ACPI memory region. I implemented some functions around
the e820 table for being able to add RAM and reserve memory regions from
it. I have so far not removed the libxc e820 table creation, but use it
to compare the results. I first dump the e820 table created by libxc in
hvmloader and then write over it and let vmxassist dump it again.
The patch imports a lot of code from vmxassist, such as functions like
printf.

There's one problem, though, and that is when the table is created in
libxc, the amount of bytes available to an HVM domain is on my test
machine 0xbffd000 bytes for a 192MB domain, which is correct according
to the calculation done in libxc where 3 pages at the highest end are
cut off. When I use the hypercall in hvmloader/e820.c to read the number
of pages available to a domain I get a number that leads to 0x20000
bytes less in that domain, 0xbfdd000. What happend to those 128kb?

Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxx>

Attachment: e820-move.diff
Description: Text Data

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