From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: 2.6.20.3 to be the next kernel? Date: Mon, 04 Jun 2007 21:57:51 -0700 Message-ID: <4664ED4F.2050006@goop.org> References: <1180961068.5786.188.camel@localhost.localdomain> <200706042058.37449.mark.williamson@cl.cam.ac.uk> <466472E4.9000505@goop.org> <200706050324.26723.mark.williamson@cl.cam.ac.uk> <4664EB80.2080509@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4664EB80.2080509@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: tim.post@netkinetics.net, "Daniel P. Berrange" , xen-devel@lists.xensource.com, Mark Williamson , Ian Campbell List-Id: xen-devel@lists.xenproject.org Jeremy Fitzhardinge wrote: > So, its all a bit of an open question. > Oh, I meant to say, the UNSW/Gelato folks have been proposing a more abstracted pagetable interface which should hide all the architectural details of the pagetable from the core kernel. That's probably the right way to go to make PAE/non-PAE runtime switchable (their actual goal is to make efficient use of the myriad ia64 pagetable modes, which makes PAE rather trivial by comparison). But I don't know what the state of those patches is - I don't think they've been posted in a while. J