michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc: use simpler words for describing scheduling

Browse source 
Use simple terms when possible.
'inhibit' -> 'prevent'
'supplanted' -> 'replaced'

Signed-off-by: Håkon Øye Amundsen <haakon.amundsen@nordicsemi.no>
This commit is contained in:
Håkon Øye Amundsen 2019-10-08 13:36:26 +00:00 • committed by Andrew Boie
commit f20127c137
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
doc/reference/kernel/scheduling/index.rst
View file

@ -13,7 +13,7 @@ The scheduler determines which thread is allowed to execute
at any point in time; this thread is known as the **current thread**. at any point in time; this thread is known as the **current thread**.
Whenever the scheduler changes the identity of the current thread, Whenever the scheduler changes the identity of the current thread,
or when execution of the current thread is supplanted by an ISR, or when execution of the current thread is replaced by an ISR,
the kernel first saves the current thread's CPU register values. the kernel first saves the current thread's CPU register values.
These register values get restored when the thread later resumes execution. These register values get restored when the thread later resumes execution.
@ -27,7 +27,7 @@ exist, the scheduler chooses the one that has been waiting longest.
.. note:: .. note::
Execution of ISRs takes precedence over thread execution, Execution of ISRs takes precedence over thread execution,
so the execution of the current thread may be supplanted by an ISR so the execution of the current thread may be replaced by an ISR
at any time unless interrupts have been masked. This applies to both at any time unless interrupts have been masked. This applies to both
cooperative threads and preemptive threads. cooperative threads and preemptive threads.
@ -125,7 +125,7 @@ becomes the current thread, its non-preemptible status is maintained.
.. note:: .. note::
Locking out the scheduler is a more efficient way for a preemptible thread Locking out the scheduler is a more efficient way for a preemptible thread
to inhibit preemption than changing its priority level to a negative value. to prevent preemption than changing its priority level to a negative value.
.. _metairq_priorities: .. _metairq_priorities: