From: "W. Michael Petullo" <mike@flyn.org>
To: xen-devel@lists.xensource.com
Subject: Re: Question about MMUEXT_PIN_L3_TABLE
Date: Fri, 9 Jul 2010 06:23:27 -0500 [thread overview]
Message-ID: <20100709112327.GA1818@imp.local> (raw)
In-Reply-To: <C85B7FA8.1A0CF%keir.fraser@eu.citrix.com>
>> (XEN) mm.c:1185:d13 PAE L3 slot is shared
>> (XEN) mm.c:1393:d13 Failure in alloc_l3_table: entry 4
>> (XEN) mm.c:2070:d13 Error while validating mfn 79f0a (pfn 4c2) for type
>> 60000000: caf=80000003 taf=60000001
>> (XEN) mm.c:2700:d13 Error while pinning mfn 79f0a
>>
>> I have not yet had any luck finding the cause of this. From what I
>> can tell, the kernel's page tables are valid. The kernel initializes
>> memory and performs many other initializations successfully before this
>> point. Does anyone have any suggestions?
> 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? Could you provide some insigt into why this is required? Do
I need to pin the L2 page directory before I pin the L3 page directory
pointer table?
--
Mike
:wq
next prev parent reply other threads:[~2010-07-09 11:23 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 [this message]
2010-07-09 11:40 ` Keir Fraser
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=20100709112327.GA1818@imp.local \
--to=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).