User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Wed, 25 Jun 2008 19:45:36 +0100
Subject: Re: [Xen-devel] Re: [PATCH 00 of 36] x86/paravirt: groundwork for
 64-bit Xen support
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Andi Kleen <andi@firstfloor.org>, Jeremy Fitzhardinge <jeremy@goop.org>
CC: Mark McLoughlin <markmc@redhat.com>,
       xen-devel <xen-devel@lists.xensource.com>,
       Eduardo Habkost <ehabkost@redhat.com>,
       LKML <linux-kernel@vger.kernel.org>, Stephen Tweedie <sct@redhat.com>
Message-ID: <C48850E0.231A8%keir.fraser@eu.citrix.com>
Thread-Topic: [Xen-devel] Re: [PATCH 00 of 36] x86/paravirt: groundwork
 for 64-bit Xen support
Thread-Index: AcjW86fC5gcDXELmEd2ISwAX8io7RQ==
In-Reply-To: <87skv1r8ln.fsf@basil.nowhere.org>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 667
Lines: 19

On 25/6/08 13:40, "Andi Kleen" <andi@firstfloor.org> wrote:

>> to 0xffff880000000000.  I have no general justification for this: th
> 
> This will significantly decrease the maximum amount of physical
> memory supported by Linux longer term.

What does Linux expect to scale up to? Reserving 16 PML4 entries leaves the
kernel with 120TB of available 'negative' address space. Should be plenty, I
would think.

 -- Keir


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/