From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "W. Michael Petullo" <mike@flyn.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Question about MMUEXT_PIN_L3_TABLE
Date: Fri, 9 Jul 2010 12:40:05 +0100 [thread overview]
Message-ID: <C85CC925.1A3E2%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <20100709112327.GA1818@imp.local>
On 09/07/2010 12:23, "W. Michael Petullo" <mike@flyn.org> wrote:
>> The fourth L2 page directory (that is, the one pointed at by the fourth and
>> final L3 pgdir entry) must not be shared by multiple L3 page directories.
>> You need one such L2 pogdir for every L3 pgdir. Many OSes would normally
>> share these, and will need modifying to not do so.
>
> As I understand this, I must create a new L2 page directory for my process
> and copy the entries in the corresponding kernel PD into it. Is this
> correct?
Yes.
>Could you provide some insigt into why this is required?
Xen owns private entries at the end of the fourth L2 page directory. Four of
these private entries map the contents of the L3 page directory entries
(yes, really) and obviously this arrangement only allows that fourth L2 page
directory to be mapped by one L3 page directory. Hence the unusual
restriction.
> Do
> I need to pin the L2 page directory before I pin the L3 page directory
> pointer table?
No. It gets implicitly pinned by the fact that it is mapped by a pinned L3.
-- Keir
prev parent reply other threads:[~2010-07-09 11:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 10:57 Question about MMUEXT_PIN_L3_TABLE W. Michael Petullo
2010-07-08 12:14 ` Keir Fraser
2010-07-09 11:23 ` W. Michael Petullo
2010-07-09 11:40 ` Keir Fraser [this message]
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=C85CC925.1A3E2%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=mike@flyn.org \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).