forked from Imagelibrary/rtems
0221da5f56
The rate monotonic period statistics were affected by rtems_cpu_usage_reset(). The logic to detect and work around a CPU usage reset was broken. The Thread_Contol::cpu_time_used is changed to contain the processor time used throughout the entire lifetime of the thread. The new member Thread_Contol::cpu_time_used_at_last_reset is added to contain the processor time used at the time of the last reset through rtems_cpu_usage_reset(). This decouples the resets of the CPU usage and the rate monotonic period statistics. Update #4528.
This directory contains code to report and reset per-task CPU usage.
If the BSP supports nanosecond timestamp granularity, this this information
is very accurate. Otherwise, it is dependendent on the tick granularity.
It provides two primary features:
+ Generate a CPU Usage Report
+ Reset CPU Usage Information
NOTES:
1. If configured for tick granularity, CPU usage is "docked" by a
clock tick at each context switch.
2. If configured for nanosecond granularity, no work is done at each
clock tick. All bookkeeping is done as part of a context switch.