forked from Imagelibrary/rtems
300f6a481a
Add priority nodes which contribute to the overall thread priority. The actual priority of a thread is now an aggregation of priority nodes. The thread priority aggregation for the home scheduler instance of a thread consists of at least one priority node, which is normally the real priority of the thread. The locking protocols (e.g. priority ceiling and priority inheritance), rate-monotonic period objects and the POSIX sporadic server add, change and remove priority nodes. A thread changes its priority now immediately, e.g. priority changes are not deferred until the thread releases its last resource. Replace the _Thread_Change_priority() function with * _Thread_Priority_perform_actions(), * _Thread_Priority_add(), * _Thread_Priority_remove(), * _Thread_Priority_change(), and * _Thread_Priority_update(). Update #2412. Update #2556.
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.