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


Re: [Xen-devel] x86_64 platform : addresses type

To: PUCCETTI Armand <armand.puccetti@xxxxxx>
Subject: Re: [Xen-devel] x86_64 platform : addresses type
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 4 Jul 2006 11:53:49 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 04 Jul 2006 03:54:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <44AA4287.9090307@xxxxxx>
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>
References: <44AA4287.9090307@xxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

However, on x86_64 using gcc, addresses as well as unsigned long are 64 bits long.

It seems that luckily mmap_addr is below 2*32-1, making the u32 type acceptable so far (for instance in function __start_xen, where the memory map is turned into
 another structure) but what would it cost to change it into u64 ?
After all, the multiboot specification (page 18) has 'unsigned long' instead of u32 here.

That info will never be placed above 4GB, or the info would not be available to non-pae non-x86/64 OSes.

 -- Keir

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>