On Thu, 2020-02-13 at 13:54 +0100, Juergen Gross wrote: > Instead of using the normal locks use the keyhandler provided > trylocks > with timeouts. This requires a special primitive for the scheduler > lock. > So, FWIW, I tend to agree with Andrew on the general aspects of this. I.e., I personally don't think that the added complexity, however small one may judge it to be, is worth it... I'm not even sure not using regular locks is really an improvement.
When you mentioned, in your other mail, that having something like this would have saved a lot of reboots during the development of core- scheduling, would _just_ disabling the watchdog have achieved the same? Anyway, I've had a look at this patch. _If_ we go with this new lock thing, the modifications to the scheduler code done here seems fine to me. Regards -- Dario Faggioli, Ph.D http://about.me/dario.faggioli Virtualization Software Engineer SUSE Labs, SUSE https://www.suse.com/ ------------------------------------------------------------------- <<This happens because _I_ choose it to happen!>> (Raistlin Majere)
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
