Lines Matching full:threads

9 User mode threads are considered to be untrusted by Zephyr and are therefore
10 isolated from other user mode threads and from the kernel. A flawed or
22   cannot compromise the kernel or other threads.
25   with their own group of threads and private data structures, which are
31 For threads running in a non-privileged CPU state (hereafter referred to as
52       threads in the same memory domain, depending on hardware.
54        - On MPU systems, threads may only access their own stack buffer.
56        - On MMU systems, threads may access any user thread stack in the same
59   - By default, program text and read-only data are accessible to all threads
62   - User threads by default are not granted default access to any memory
93 - We prevent the introduction of new executable code by user mode threads,
98 - The kernel itself, and any threads that are executing in supervisor mode,
113 - It is possible to make top-level declarations of user mode threads and
120   particular priority can starve all threads of lower priority, and also other
121   threads of the same priority if time-slicing is not enabled.
123 - There are build-time defined limits on how many threads can be active
124   simultaneously, after which creation of new user threads will fail.
126 - Stack overflows for threads running in supervisor mode may be caught,
140   threads inherit the memory domain configuration of the parent. Threads may
144 - User threads cannot directly access memory belonging to kernel objects.
147   drivers and threads stacks are also considered kernel objects. This ensures
151 - User threads by default have no permission to access any kernel object or
155   The creation of new threads has an option to automatically inherit