Lines Matching +full:permission +full:- +full:flags

29 Permission on an object also has the semantics of a reference to an object.
36   may be called to release any runtime-allocated buffers the object was using.
52 * The object must be declared as a top-level global at build time, such that it
54   with static scope. The post-build script :ref:`gen_kobject_list.py` scans the
60   must not be located in any memory partitions that are user-accessible.
71 information will be printed if the script is run with the ``--verbose`` flag,
88   may drop their own permission on an object with
96 the access control aspects of the permission system are not enforced.
101 The :ref:`gen_kobject_list.py` script is a post-build step which finds all the
110 with a constant-time lookup in this table.
123   numerical ID assigned to them at build time, used to index the permission
124   bitfield for an object to see if that thread has permission on it. The size
129 * A set of flags for that object. This is currently used to track
137 Supervisor Thread Access Permission
151 User Thread Access Permission
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
165   :c:func:`k_object_access_grant` API. The convenience pseudo-function
169   permission, or the object whose access is being granted, do not need to be
190 not being tracked by the kernel will be no-ops. Doing the same from user mode
194 permission on the allocated object to the calling thread.
218 .. code-block:: c