zephyr/tests/kernel/threads
Peter Mitsis 5710e034e7 kernel: Introduce _THREAD_SLEEPING state bit
At the present time, Zephyr does has overlap between sleeping and
suspending. Not only should sleeping and suspended be orthogonal
states, but we should ensure users always employ the correct API.
For example, to wake a sleeping thread, k_wakeup() should be used,
and to resume a suspended thread, k_thread_resume() should be used.
However, at the present time k_thread_resume() can be used on a
thread that called k_sleep(K_FOREVER). Sleeping should have nothing
to do with suspension.

This commit introduces the new _THREAD_SLEEPING thread state along
with some prep-work to facilitate the decoupling of the sleeping and
suspended thread states.

Signed-off-by: Peter Mitsis <peter.mitsis@intel.com>
2024-12-18 18:17:03 +01:00
..
dynamic_thread
dynamic_thread_stack samples, tests: remove usage of space-separated lists 2024-12-04 14:14:53 -05:00
no-multithreading
thread_apis kernel: Introduce _THREAD_SLEEPING state bit 2024-12-18 18:17:03 +01:00
thread_error_case tests: thread_error_case: fix incorrect userspace filtering 2024-11-20 15:58:15 -05:00
thread_init
thread_stack
tls arch: kernel: lib: toolchain: Standardize TLS keyword 2024-09-23 10:01:48 +02:00