Lines Matching refs:thread

8 * A core kernel object, such as a semaphore, thread, pipe, etc.
9 * A thread stack, which is an array of :c:struct:`z_thread_stack_element`
26 that the kernel object address is valid and that the calling thread
49 In order for a static kernel object to be usable by a user thread via system
80 the calling thread's resource pool. Such allocations may be freed in two
90   cleared when a thread terminates. Supervisor threads may additionally
91   revoke references for another thread using
124   bitfield for an object to see if that thread has permission on it. The size
143 * If a supervisor thread calls :c:func:`k_thread_user_mode_enter`, the
144   thread will then run in user mode with any permissions it had been granted
145   (in many cases, by itself) when it was a supervisor thread.
147 * If a supervisor thread creates a user thread with the
148   :c:macro:`K_INHERIT_PERMS` option, the child thread will be granted the
149   same permissions as the parent thread, except the parent thread object.
154 By default, when a user thread is created, it will only have access permissions
155 on its own thread object. Other kernel objects by default are not usable.
159 * If a thread is created with the :c:macro:`K_INHERIT_PERMS`, that thread
160   will inherit all the permissions of the parent thread, except the parent
161   thread object.
163 * A thread that has permission on an object, or is running in supervisor mode,
164   may grant permission on that object to another thread via the
168   :c:func:`k_object_access_grant` on each of them. The thread being granted
171   have permissions on both the kernel object and the target thread object.
179 * If a thread was declared statically with :c:macro:`K_THREAD_DEFINE()`,
180   then the :c:macro:`K_THREAD_ACCESS_GRANT()` may be used to grant that thread
183 Once a thread has been granted access to an object, such access may be
191 will result in a fatal error for the calling thread.
194 permission on the allocated object to the calling thread.
214 thread, otherwise the kernel will consider the object uninitialized if accessed
215 by a user thread. This is very uncommon, typically only for kernel objects that