Hi,Could this also eliminate/address the busy-loop hack in timer_read in time.c?
And another question: Why you remove only 1 extra jiffy in the timer callbacks and not all the extra jiffies? Is there always only 1 or could there be multiple?
regards Benjamin Beichler Am 13.09.2024 um 22:17 schrieb Benjamin Berg:
From: Benjamin Berg <benjamin.b...@intel.com> In time-travel mode userspace can do a lot of work without any time passing. Unfortunately, this can result in OOM situations as the RCU core code will never be run. Work around this by keeping track of userspace processes that do not yield for a lot of operations. When this happens, insert a jiffie into the sched_clock clock to account time against the process and cause the bookkeeping to run. As sched_clock is used for tracing, it is useful to keep it in sync between the different VMs. As such, try to remove added ticks again when the actual clock ticks.
OpenPGP_0x1569BBF90AC3918A.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
