From: "H. Peter Anvin" <hpa@linux.intel.com>
To: stefano.stabellini@eu.citrix.com
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
konrad.wilk@oracle.com, jeremy@goop.org, yinghai@kernel.org,
mingo@elte.hu, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 2/4] x86,xen: introduce x86_init.mapping.pagetable_reserve
Date: Wed, 13 Apr 2011 11:26:44 -0700 [thread overview]
Message-ID: <4DA5EAE4.2060406@linux.intel.com> (raw)
In-Reply-To: <1302607192-21355-2-git-send-email-stefano.stabellini@eu.citrix.com>
On 04/12/2011 04:19 AM, stefano.stabellini@eu.citrix.com wrote:
> From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
> Introduce a new x86_init hook called pagetable_reserve that during the
> initial memory mapping is used to reserve a range of memory addresses for
> kernel pagetable usage.
>
> On native it just calls memblock_x86_reserve_range while on xen it also
> takes care of setting the spare memory previously allocated
> for kernel pagetable pages from RO to RW, so that it can be used for
> other purposes.
>
What are the *semantics* of this hook?
Hooks are insanely nasty if they are just defined by a particular code
flow, as evidenced by the royal mess called paravirt_ops.
-hpa
next prev parent reply other threads:[~2011-04-13 18:27 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 11:16 [PATCH 0/4] xen: critical bug fixes for 2.6.39-rc3 Stefano Stabellini
2011-04-12 11:16 ` Stefano Stabellini
2011-04-12 11:19 ` [PATCH 1/4] xen: mask_rw_pte mark RO all pagetable pages up to pgt_buf_top stefano.stabellini
2011-04-12 16:47 ` Konrad Rzeszutek Wilk
2011-04-12 16:47 ` Konrad Rzeszutek Wilk
2011-04-13 10:24 ` Stefano Stabellini
2011-04-12 11:19 ` [PATCH 2/4] x86,xen: introduce x86_init.mapping.pagetable_reserve stefano.stabellini
2011-04-12 11:50 ` [Xen-devel] [PATCH 2/4] x86, xen: " Jan Beulich
2011-04-12 11:50 ` Jan Beulich
2011-04-12 17:41 ` Stefano Stabellini
2011-04-12 17:41 ` Stefano Stabellini
2011-04-12 17:40 ` [PATCH 2/4] x86,xen: " Yinghai Lu
2011-04-13 10:35 ` Stefano Stabellini
2011-04-13 10:35 ` Stefano Stabellini
2011-04-13 18:28 ` H. Peter Anvin
2011-04-14 11:05 ` Stefano Stabellini
2011-04-13 18:03 ` Konrad Rzeszutek Wilk
2011-04-13 18:35 ` H. Peter Anvin
2011-04-13 18:35 ` [PATCH 2/4] x86, xen: " H. Peter Anvin
2011-04-13 20:19 ` [PATCH 2/4] x86,xen: " Konrad Rzeszutek Wilk
2011-04-13 18:26 ` H. Peter Anvin [this message]
2011-04-14 11:30 ` Stefano Stabellini
2011-04-14 14:49 ` Stefano Stabellini
2011-04-14 14:49 ` Stefano Stabellini
2011-04-14 14:52 ` H. Peter Anvin
2011-04-14 18:09 ` Stefano Stabellini
2011-04-18 14:09 ` Stefano Stabellini
2011-04-18 14:42 ` H. Peter Anvin
2011-04-18 17:21 ` Stefano Stabellini
2011-04-20 16:50 ` Jeremy Fitzhardinge
2011-04-12 11:19 ` [PATCH 3/4] xen: more debugging in the e820 parsing stefano.stabellini
2011-04-12 16:39 ` Konrad Rzeszutek Wilk
2011-04-13 10:24 ` Stefano Stabellini
2011-04-13 17:54 ` Konrad Rzeszutek Wilk
2011-04-14 10:35 ` Stefano Stabellini
2011-04-12 11:19 ` [PATCH 4/4] xen: do not create the extra e820 region at an addr lower than 4G stefano.stabellini
2011-04-12 16:48 ` Konrad Rzeszutek Wilk
2011-04-12 16:48 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DA5EAE4.2060406@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.