Il 27/06/2013 13:43, Gleb Natapov ha scritto: >>> > > I am copying Jan, the author of the patch. Commit message says: >>> > > "Code under this lock requires non-preemptibility", but which code >>> > > exactly is this? Is this still true? >> > >> > hardware_enable_nolock/hardware_disable_nolock does. >> > > I suspected this will be the answer and prepared another question :) > From a glance kvm_lock is used to protect those just to avoid creating > separate lock, so why not create raw one to protect them and change > kvm_lock to non raw again. Admittedly I haven't looked too close into > this yet.
I was wondering the same, but I think it's fine. There's just a handful of uses outside virt/kvm/kvm_main.c. Paolo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
