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] linux/x86-64: allow kernel init memory to be fre

To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] linux/x86-64: allow kernel init memory to be freed
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Fri, 02 Mar 2007 16:19:22 +0000
Delivery-date: Fri, 02 Mar 2007 08:18:38 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45E85870.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: Acdc5olax7kmiMjZEduwRgAX8io7RQ==
Thread-topic: [Xen-devel] [PATCH] linux/x86-64: allow kernel init memory to be freed
User-agent: Microsoft-Entourage/11.2.5.060620
On 2/3/07 16:01, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> The mappings in the direct map area must be writeable and, as the comment
> says, make_readonly() forces all kernel space mappings to be set up as
> read-only during boot. Thus this does *not* depend on
> XENFEAT_writable_page_tables, unless make_readonly() is changed.

Ok, understood.

> So - would you be okay with taking the full-blown patch (probably not, as it
> touches another file not currently in the sparse tree), or should I create a
> __make_page_inaccessible() function along the lines of
> __make_page_readonly()/__make_page_writable()?

Yeah, I'll go with __make_page_inaccessible(). :-)

 -- Keir


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