Andy Ross d8421adadd kernel/timeout: Fix synchronization in z_tick_get_32() ... The previous comment correctly and carefully explained why the 64 bit value in curr_tick doesn't require locking when reading only the low 32 bits. It completely missed the fact that the calculation of elapsed time and the read of curr_tick ABSOLUTELY DO require locking, because the former is expressed in terms of the latter. This was always bug, even in the old code, but never witnessed because we ran so little software in tickless mode. Signed-off-by: Andy Ross <andrew.j.ross@intel.com>		2018-10-16 15:03:10 -04:00
..
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
system_work_q.c
thread_abort.c
thread.c
timeout.c	kernel/timeout: Fix synchronization in z_tick_get_32()	2018-10-16 15:03:10 -04:00
timer.c
userspace_handler.c
userspace.c
version.c
work_q.c