From: Andi Kleen <ak@suse.de>
To: xen-merge@lists.xensource.com
Cc: Xen Mailing List <xen-devel@lists.xensource.com>,
Jun Nakajima <jun.nakajima@intel.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: [Xen-merge] Re: x86-64's __PAGE_OFFSET
Date: Fri, 6 Jan 2006 21:40:39 +0100 [thread overview]
Message-ID: <200601062140.40045.ak@suse.de> (raw)
In-Reply-To: <43BEB2D9.76F0.0078.0@novell.com>
On Friday 06 January 2006 18:11, Jan Beulich wrote:
> >>> Keir Fraser <Keir.Fraser@cl.cam.ac.uk> 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
prev parent reply other threads:[~2006-01-06 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 13:50 x86-64's __PAGE_OFFSET Jan Beulich
2006-01-06 14:10 ` Keir Fraser
2006-01-06 17:11 ` Jan Beulich
2006-01-06 20:40 ` Andi Kleen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200601062140.40045.ak@suse.de \
--to=ak@suse.de \
--cc=JBeulich@novell.com \
--cc=jun.nakajima@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-merge@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.