| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] About the page lock while updating mmu.
Oh, Keir and Jan, there is some misunderstanding in my former mail, please
ignore it, sorry for inconvenience.
Best Regards,
-- Dongxiao
-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Xu, Dongxiao
Sent: 2008年6月26日 11:58
To: Keir Fraser; jbeulich@xxxxxxxxxx; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] About the page lock while updating mmu.
Hi, Keir and Jan,
In C/S 17846, page lock is used instead of the per-domain lock. It
uses the spin lock in page_info structure to ensure the unique access
into the page. But while updating mmu (l1_entry, l2_entry, l3_entry,
l4_entry), I think these pages should be described by shadow_page_info,
but not page_info. However there is no spin lock defined in
shadow_page_info structure.
This may be the root cause for Xen bug 1278:
(On 32E, XenU guest can not boot up after destorying a HVM guest.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1278)
Best Regards,
-- Dongxiao
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home