Niklas Hauser
103ddb5b3d
cpuload: Fix wrong idle thread load
...
When the CPU load monitor is started while already running, then the
idle thread last_times[0] is reset to the last 1 second, rather than
since when the CPU load monitor was last started. The remaining threads
are not impacted, since their last_times[i] is reset to zero here.
This results in the idle thread having a lower than real CPU load, with
the remaining CPU time being wrongly attributed as scheduler load.
2024-01-31 07:52:59 +01:00
..
2023-03-16 11:55:45 +01:00
2023-12-21 11:34:28 +01:00
2023-08-08 12:28:52 -04:00
2023-12-01 13:11:00 -05:00
2022-11-14 09:26:14 -05:00
2024-01-30 11:20:19 -05:00
2024-01-26 15:17:54 +01:00
2024-01-30 11:25:37 -05:00
2023-12-21 16:27:53 +01:00
2024-01-30 11:23:55 -05:00
2022-10-13 16:05:25 -04:00
2023-12-21 16:50:13 +01:00
2023-12-21 11:34:28 +01:00
2023-12-21 13:52:47 +01:00
2024-01-29 09:45:40 +01:00
2024-01-17 14:44:11 +01:00
2024-01-30 11:28:20 -05:00
2022-11-30 14:50:13 -05:00
2023-11-20 14:52:35 +01:00
2023-09-19 09:12:40 +02:00
2022-10-05 14:21:38 -04:00
2023-10-31 10:02:18 -04:00
2024-01-31 07:52:59 +01:00
2022-10-19 19:09:20 +02:00
2023-12-08 21:17:59 +01:00
2024-01-30 11:25:37 -05:00
2024-01-12 09:51:55 +01:00
2023-12-21 13:52:47 +01:00
2023-11-30 17:16:02 +01:00
2023-09-20 17:45:07 -04:00
2024-01-18 12:14:17 -05:00
2024-01-30 11:25:37 -05:00
2023-03-16 11:55:45 +01:00
2023-12-01 13:11:00 -05:00
2023-07-13 12:00:35 +02:00
2023-12-01 13:11:00 -05:00
2023-11-28 16:30:17 +01:00
2024-01-09 10:20:40 -05:00
2023-12-21 16:27:53 +01:00
2024-01-29 20:44:12 -05:00
2024-01-29 17:04:10 +01:00
2023-03-16 11:55:45 +01:00
2023-12-21 16:27:53 +01:00
2024-01-18 08:55:28 +01:00
2024-01-24 21:51:05 -05:00