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

Re: [Xen-devel] Question about MMUEXT_PIN_L3_TABLE


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "W. Michael Petullo" <mike@xxxxxxxx>
  • Date: Fri, 9 Jul 2010 06:23:27 -0500
  • Delivery-date: Fri, 09 Jul 2010 04:20:20 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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