On Wed, 7 May 2008, Christoph Lameter wrote:
>
> Set the vma flag when we locked it and then skip when we find it locked
> right? This would be in addition to the global lock?
Yes. And clear it before unlocking (and again, testing if it's already
clear - you mustn't unlock twice, so you must only unlock when the bit
was set).
You also (obviously) need to have somethign that guarantees that the lists
themselves are stable over the whole sequence, but I assume you already
have mmap_sem for reading (since you'd need it anyway just to follow the
list).
And if you have it for writing, it can obviously *act* as the global lock,
since it would already guarantee mutual exclusion on that mm->mmap list.
Linus
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
