pá 27. 2. 2026 v 16:51 odesílatel Steven Rostedt <[email protected]> napsal: > > Example: > > > > osnoise/timerlat_period is set to 1000, osnoise/timerlat_align_us is > > set to 50. There are four threads, on CPUs 1 to 4. > > Is it set to 50 or 20? >
That is a typo, good catch. > > So the first one here sets 'align_next' and all others fall into this path. > > As 'align_next' is a static variable for this function, what happens if you > run timerlat a second time with different values? > That is an oversight. It worked during my testing, since timerlat took the align_next of the previous run, and since it was far in the past, it incremented it to be in the future, and everything worked. But that is not the intended behavior (and will be slow if a lot of time passes between the timerlat runs, since we increment it multiple times by the period) It should be a global variable reset with each run. I got too excited about the patch and forgot this is not RTLA where static variables get reset with each run (unless I want the user to reboot after each run). I will fix it. Tomas
