Hi, PGT_locked can mutually exclude CPUs trying to work on the same page. I have a few questions 1. shouldn''t page_lock/unlock call preempt_disable/enable respectively? 2. It seems to be used only for pv page table self-updates. Is there any obscure reason its usage is confined to only this, any dark secrets why it can''t be used elsewhere? And here is my plan 1. remove horrible global shr_lock by following up on Adin Scannell''s removal of the sharing hash table 2. Still, concurrent additions/deletions of gfn_info list elements to a shared page need to be protected. I''m thinking of using PGT_locked for this. Sounds good? Thanks Andres _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel