Lines Matching full:threads

17 Kernel objects are completely opaque to user threads. User threads work
21 user threads.
23 Since user threads may not directly manipulate kernel objects, all use of
44 Kernel objects that are only used by supervisor threads have no restrictions
46 to prevent accidental or intentional corruption by user threads, they must
47 not be located in any memory that user threads have direct access to.
83 * Supervisor threads may call :c:func:`k_object_free` to force a dynamic
86 * If an object's references drop to zero (which happens when no threads have
87   permissions on it) the object will be automatically freed. User threads
90   cleared when a thread terminates. Supervisor threads may additionally
95 supervisor threads to acquire permissions on objects they are using even though
122 * A bitfield indicating permissions on that object. All threads have a
140 Supervisor threads can access any kernel object. However, permissions for
141 supervisor threads are still tracked for two reasons:
173 * Supervisor threads may declare a particular kernel object to be a public
174   object, usable by all current and future threads with the
185 available to user threads, however user threads may use