mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-14 22:51:57 +00:00
9ecc4ead68
When adding a new runnable thread in tickless mode, we need to detect whether it will timeslice with the running thread and reset the timer, otherwise it won't get any CPU time until the next interrupt fires at some indeterminate time in the future. This fixes the specific bug discussed in #7193, but the broader problem of tickless and timeslicing interacting badly remains. The code as it exists needs some rework to avoid all the #ifdef mess. Signed-off-by: Andy Ross <andrew.j.ross@intel.com> |
||
|---|---|---|
| .. | ||
| include | ||
| alert.c | ||
| atomic_c.c | ||
| CMakeLists.txt | ||
| compiler_stack_protect.c | ||
| device.c | ||
| errno.c | ||
| idle.c | ||
| init.c | ||
| int_latency_bench.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 | ||
| sys_clock.c | ||
| system_work_q.c | ||
| thread_abort.c | ||
| thread.c | ||
| timer.c | ||
| userspace_handler.c | ||
| userspace.c | ||
| version.c | ||
| work_q.c | ||