From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xensource.com>
Subject: Re: [PATCH] linux/x86-64: allow kernel init memory to
	be freed
Date: Fri, 02 Mar 2007 16:19:22 +0000
Message-ID: <C20DFF0A.A837%keir@xensource.com>
References: <45E85870.76E4.0078.0@novell.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <45E85870.76E4.0078.0@novell.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jan Beulich <jbeulich@novell.com>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On 2/3/07 16:01, "Jan Beulich" <jbeulich@novell.com> 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