Chris O'Byrne - YAVRTOS |
||||||||||||||||||||||||||||||||||||||||||||
|
The possible states that a task can be in
Detailed DescriptionFor internal use only. These are the states that a task can be in (i.e. the possible values of task.status). Define Documentation
Cleaning up. The task is stopping, and the stack contains the entire CPU context This state is set by the scheduler the first time the task is scheduled after having had its state set to TASK_STATE_STOPPING
Running. The task is running, and the stack contains the entire CPU context. This state is set by the scheduler the first time the task is scheduled
Starting. The task is starting, and the stack only contains a return address for task_starter() This state is set by create_task()
Stopped. The task is completely dead, and this entry in the task list is available for new tasks. This state is set by reserve_task(), and when the task has completely stopped.
Stopping. The task is stopping, and the stack only contains a return address for task_stopper() This state is set by stop_task() when there is no need, or desire, to wait for mutexes. Note that a task will commit suicide on lock_off() if it is in TASK_STATE_WAITING_TO_STOP and has just released its last mutex.
Waiting for the task to release all of its mutexes before stopping. The task is running, and the stack contains the entire CPU context
This state is set by stop_task() when the
|
|||||||||||||||||||||||||||||||||||||||||||
YAVRTOS and YAVRTOS documentation Copyright © 2007-2008 Chris O'Byrne. Email - chris <at> obyrne <dot> com