doc: threads: Clarify ready/running states
Updates the threads documentation to clarify the distinction between ready and running states. Fixes 44255 Signed-off-by: Peter Mitsis <peter.mitsis@intel.com>
This commit is contained in:
parent
195072dcd1
commit
111865a8c5
1 changed files with 6 additions and 1 deletions
|
@ -156,10 +156,15 @@ The following factors make a thread unready:
|
||||||
* The thread has been suspended.
|
* The thread has been suspended.
|
||||||
* The thread has terminated or aborted.
|
* The thread has terminated or aborted.
|
||||||
|
|
||||||
|
|
||||||
.. image:: thread_states.svg
|
.. image:: thread_states.svg
|
||||||
:align: center
|
:align: center
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
Although the diagram above may appear to suggest that both **Ready** and
|
||||||
|
**Running** are distinct thread states, that is not the correct
|
||||||
|
interpretation. **Ready** is a thread state, and **Running** is a
|
||||||
|
schedule state that only applies to **Ready** threads.
|
||||||
|
|
||||||
Thread Stack objects
|
Thread Stack objects
|
||||||
********************
|
********************
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue