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-devel] [PATCH 0/8] 2.6.17 merge additions

To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0/8] 2.6.17 merge additions
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Fri, 02 Mar 2007 11:17:05 +0000
Delivery-date: Fri, 02 Mar 2007 03:16:24 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45E80393.76E4.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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdcvE7cjTGOscivEduwRgAX8io7RQ==
Thread-topic: [Xen-devel] [PATCH 0/8] 2.6.17 merge additions
User-agent: Microsoft-Entourage/11.2.5.060620


On 2/3/07 09:59, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> Isn't that patch just doing this -  paging_init() is almost identical to
> native
> after the patch (the sole difference is the setting of
> init_mm.context.pinned).
> The only real addition (to find_early_table_space()) is the space reservation
> for the fixmap tables (so these can be set up earlier) and the stuff moved
> out of paging_init() into init_memory_mapping(). And I don't think it is
> reasonable to expect init_memory_mapping() to get very close to native.

Okay I probably should have done a three-way comparison with the native code
as well, then. My first impression was definitely that the code looked more
complicated rather than less. :-) I'll take another look.

 -- Keir


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

<Prev in Thread] Current Thread [Next in Thread>