Caller| Name | Describe |
|---|
| update_stats_wait_start | |
| update_stats_wait_end | |
| update_stats_enqueue_sleeper | |
| update_stats_dequeue | |
| task_non_contending | The utilization of a task cannot be immediately removed from* the rq active utilization (running_bw) when the task blocks |
| setup_new_dl_entity | We are being explicitly informed that a new instance is starting,* and this means that:* - the absolute deadline of the entity has to be placed at* current time + relative deadline;* - the runtime of the entity has to be set to the maximum value |
| replenish_dl_entity | Pure Earliest Deadline First (EDF) scheduling does not deal with the* possibility of a entity lasting more than what it declared, and thus* exhausting its runtime |
| update_dl_revised_wakeup | Revised wakeup rule [1]: For self-suspending tasks, rather then* re-initializing task's runtime and deadline, the revised wakeup* rule adjusts the task's runtime to avoid the task to overrun its* density |
| update_dl_entity | When a deadline entity is placed in the runqueue, its runtime and deadline* might need to be updated. This is done by a CBS wake up rule. There are two* different rules: 1) the original CBS; and 2) the Revisited CBS. |
| start_dl_timer | If the entity depleted all its runtime, and if we want it to sleep* while waiting for some new execution time to become available, we* set the bandwidth replenishment timer to the replenishment instant* and try to activate it |
| dl_check_constrained_dl | During the activation, CBS checks if it can reuse the current task's* runtime and period |
| enqueue_dl_entity | |