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's __PAGE_OFFSET

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, "Jun Nakajima" <jun.nakajima@xxxxxxxxx>
Subject: Re: [Xen-devel] x86-64's __PAGE_OFFSET
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Fri, 06 Jan 2006 18:11:37 +0100
Cc: Xen Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>, Xen merge mainline list <xen-merge@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 06 Jan 2006 17:16:39 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <790630486c55d3da6ec2928847f2ca27@xxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> 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...


Xen-devel mailing list