[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] linux/x86-64: allow kernel init memory to be freed

  • To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Fri, 02 Mar 2007 16:19:22 +0000
  • Delivery-date: Fri, 02 Mar 2007 08:18:38 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acdc5olax7kmiMjZEduwRgAX8io7RQ==
  • Thread-topic: [Xen-devel] [PATCH] linux/x86-64: allow kernel init memory to be freed

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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.