Andrew Boie 348a0fda62 userspace: make mem domain lock non-static ... Strictly speaking, any access to a mem domain or its containing partitions should be serialized on this lock. Architecture code may need to grab this lock if it is using this data during, for example, context switches, especially if they support SMP as locking interrupts is not enough. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>		2020-10-20 09:37:49 -07:00
..
include	userspace: make mem domain lock non-static	2020-10-20 09:37:49 -07:00
atomic_c.c
cache_handlers.c
CMakeLists.txt
compiler_stack_protect.c
device.c
errno.c
fatal.c
futex.c
idle.c
init.c
Kconfig
kheap.c
mailbox.c
mem_domain.c	userspace: make mem domain lock non-static	2020-10-20 09:37:49 -07:00
mem_slab.c
mempool_sys.c
mempool.c
mmu.c
msg_q.c
mutex.c
pipes.c
poll.c	code-guideline: Fixing code violation 10.4 Rule	2020-10-01 17:13:29 -04:00
queue.c
sched.c	userspace: remove threads from domain on abort	2020-10-20 09:37:49 -07:00
sem.c
smp.c
stack.c	kernel: stack: fix stack_push spinlock and return	2020-10-07 17:10:36 -04:00
system_work_q.c
thread_abort.c
thread.c	userspace: remove threads from domain on abort	2020-10-20 09:37:49 -07:00
timeout.c	kernel: timer: update _timeout API for const correctness	2020-10-02 11:29:14 +02:00
timer.c	kernel: timer: update k_timer API for const correctness	2020-10-02 11:29:14 +02:00
userspace_handler.c
userspace.c
version.c
work_q.c	kernel: delayed_work: update k_delayed_work_cancel documentation	2020-10-09 11:48:00 +02:00