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-merge] Re: [Xen-devel] x86-64's __PAGE_OFFSET

To: xen-merge@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-merge] Re: [Xen-devel] x86-64's __PAGE_OFFSET
From: Andi Kleen <ak@xxxxxxx>
Date: Fri, 6 Jan 2006 21:40:39 +0100
Cc: Xen Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jun Nakajima <jun.nakajima@xxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Fri, 06 Jan 2006 22:39:20 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43BEB2D9.76F0.0078.0@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/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: <43BE839A.76F0.0078.0@xxxxxxxxxx> <790630486c55d3da6ec2928847f2ca27@xxxxxxxxxxxx> <43BEB2D9.76F0.0078.0@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8.2
On Friday 06 January 2006 18:11, Jan Beulich wrote:
> >>> Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> 06.01.06 15:10:13 >>>
> >
> >On 6 Jan 2006, at 13:50, Jan Beulich wrote:
> >
> >> What, if any, is the reason for x86-64 xenlinux to have a different
> >> __PAGE_OFFSET value than native? While merging, it would seem 
> >> reasonable
> >> to drop this difference if not motivated technically.
> >
> >Jun might remember if there was a particular reason, but I can't think
> 
> >of any insurmountable technical reason why the native __PAGE_OFFSET 
> >value shouldn't work.
> 
> There must be a reason - the system dies immediately with that change.
> But I'd really like to understand why this is so, perhaps to check with
> Andi whether then we couldn't generally go with the Xen value...

It would lose 7TB of the kernel's theoretical 63TB main memory 
support. While that exceeds the address space of all current x86-64 CPUs
(1TB max) given that there are already multi TB machines around it might 
not be a good idea.

What does Xen need that big hole for?

-Andi

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