7cdf40541b
Traditionally threads have been initialized with a PRESTART flag set, which gets cleared when the thread runs for the first time via either its timeout or the k_thread_start() API. But if you think about it, this is no different, semantically, than SUSPENDED: the thread is prevented from running until the flag is cleared. So unify the two. Start threads in the SUSPENDED state, point everyone looking at the PRESTART bit to the SUSPENDED flag, and make k_thread_start() be a synonym for k_thread_resume(). There is some mild code size savings from the eliminated duplication, but the real win here is that we make space in the thread flags byte, which had run out. Signed-off-by: Andy Ross <andyross@google.com> |
||
|---|---|---|
| .. | ||
| app_kernel | ||
| cmsis_dsp | ||
| data_structure_perf | ||
| footprints | ||
| latency_measure | ||
| mbedtls | ||
| sched | ||
| sched_queues | ||
| sched_userspace | ||
| sys_kernel | ||
| thread_metric | ||
| wait_queues | ||