mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-06 17:41:57 +00:00
4c2fc2aed7
Calling z_ready_thread() means the thread is now ready and can wake up at any moment on another CPU. But we weren't finished setting the return value! So the other side could wake up with a spurious "error" condition if it ran too soon. Note that on systems with a working IPI, that wakeup can happen much faster than you might think. Signed-off-by: Andy Ross <andrew.j.ross@intel.com> |
||
|---|---|---|
| .. | ||
| include | ||
| atomic_c.c | ||
| CMakeLists.txt | ||
| compiler_stack_protect.c | ||
| device.c | ||
| errno.c | ||
| fatal.c | ||
| futex.c | ||
| idle.c | ||
| init.c | ||
| Kconfig | ||
| Kconfig.power_mgmt | ||
| mailbox.c | ||
| mem_domain.c | ||
| mem_slab.c | ||
| mempool.c | ||
| msg_q.c | ||
| mutex.c | ||
| pipes.c | ||
| poll.c | ||
| queue.c | ||
| sched.c | ||
| sem.c | ||
| smp.c | ||
| stack.c | ||
| system_work_q.c | ||
| thread_abort.c | ||
| thread.c | ||
| timeout.c | ||
| timer.c | ||
| userspace_handler.c | ||
| userspace.c | ||
| version.c | ||
| work_q.c | ||