>>> On 02.02.16 at 07:54, <oscar.zhan...@huawei.com> wrote: > Hi all: > In patch e1e40bccee7490a01ac7d1f759ec2bbafd3c7185, it says that"many > routines can logically assert holding the p2m *FOR A SPECIFIC GFN.*" , > But I find out that it did nothing for locking a single gfn, in fact it > still locked the entire p2m list. > > -#define p2m_lock_recursive(p) mm_lock_recursive(p2m, &(p)->lock) > +#define gfn_lock(p,g,o) mm_lock_recursive(p2m, &(p)->lock) //'g' is > not > used. The entire p2m list is locked. > > > Do we have any plan to lock a specific gfn?
This indeed is a long term plan, but afaik no-one is currently doing any work in that direction. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
