Lines Matching full:permissions

27 has sufficient permissions to work with it.
87   permissions on it) the object will be automatically freed. User threads
89   :c:func:`k_object_release`, and their permissions are automatically
94 Because permissions are also used for reference counting, it is important for
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
144   thread will then run in user mode with any permissions it had been granted
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
160   will inherit all the permissions of the parent thread, except the parent
171   have permissions on both the kernel object and the target thread object.
186 :c:func:`k_object_release` to relinquish their own permissions on an
189 API calls from supervisor mode to set permissions on kernel objects that are