Benjamin Berg 887c5c12e8 um: work around sched_yield not yielding in time-travel mode ... sched_yield by a userspace may not actually cause scheduling in time-travel mode as no time has passed. In the case seen it appears to be a badly implemented userspace spinlock in ASAN. Unfortunately, with time-travel it causes an extreme slowdown or even deadlock depending on the kernel configuration (CONFIG_UML_MAX_USERSPACE_ITERATIONS). Work around it by accounting time to the process whenever it executes a sched_yield syscall. Signed-off-by: Benjamin Berg <benjamin.berg@intel.com> Link: https://patch.msgid.link/20250314130815.226872-1-benjamin@sipsolutions.net Signed-off-by: Johannes Berg <johannes.berg@intel.com>		2025-03-18 11:06:20 +01:00
..
time-internal.h	um: work around sched_yield not yielding in time-travel mode	2025-03-18 11:06:20 +01:00
virtio-uml.h	um: virtio/pci: enable suspend/resume	2021-06-17 21:45:44 +02:00