On Wed, 2018-04-11 at 13:25 +0100, George Dunlap wrote: > There are a lot of places which release a lock before calling > vcpu_sleep_nosync(), which then just grabs the lock again. This is > not only a waste of time, but leads to more code duplication (since > you have to copy-and-paste recipes rather than calling a unified > function), which in turn leads to an increased chance of bugs. > > Introduce vcpu_sleep_nosync_locked(), which can be called if you > already hold the schedule lock. > > Signed-off-by: George Dunlap <george.dun...@citrix.com> > Reviewed-by: Dario Faggioli <dfaggi...@suse.com>
Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Software Engineer @ SUSE https://www.suse.com/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
