struct WaitQueueInheritedSchedulerState

Defined at line 380 of file ../../zircon/kernel/include/kernel/scheduler_state.h

Public Members

InheritedProfileValues ipvs
Fixed start_time
Fixed finish_time
Fixed time_slice_ns
Fixed time_slice_used_ns

Public Methods

void WaitQueueInheritedSchedulerState ()

Defined at line 382 of file ../../zircon/kernel/include/kernel/scheduler_state.h

void ~WaitQueueInheritedSchedulerState ()

Defined at line 383 of file ../../zircon/kernel/include/kernel/scheduler_state.h

void Reset ()

Defined at line 385 of file ../../zircon/kernel/include/kernel/scheduler_state.h

void ResetDynamicParameters ()

If we have extra validation enabled, and this queue is no longer

inheriting any deadline pressure (even if there are still waiters),

then reset the dynamic parameters as well.

The dynamic parameters (start time, finish time, time slice) are

technically undefined when we are not inheriting any utilization. Fair

thread do not have defined dynamic parameters when they are blocked.

In a production build with no extra validation checks, it should not be

necessary to ever touch them once they become undefined. Their values

will be overwritten later on if/when they do finally become defined

again. In a build with extra checks enabled, however, it can be

beneficial to reset them to known default values when they are in the

"undefined" state, in order to make it easier to catch an accidental use

of the parameters when they have no defined meaning.

Defined at line 402 of file ../../zircon/kernel/include/kernel/scheduler_state.h

void AssertDynamicParametersAreReset ()

Defined at line 413 of file ../../zircon/kernel/include/kernel/scheduler_state.h

void AssertIsReset ()

Defined at line 424 of file ../../zircon/kernel/include/kernel/scheduler_state.h