Lines Matching refs:objects

14 The set of known kernel objects and driver subsystems is defined in
17 Kernel objects are completely opaque to user threads. User threads work
18 with addresses to kernel objects when making API calls, but may never
20 All kernel objects must be placed in memory that is not accessible by
23 Since user threads may not directly manipulate kernel objects, all use of
31 or objects which themselves have been allocated from a runtime memory pool.
44 Kernel objects that are only used by supervisor threads have no restrictions
53   appears in the ELF symbol table. It is permitted to declare kernel objects
55   generated ELF file to find kernel objects and places their memory addresses
56   in a special table of kernel object metadata.  Kernel objects may be members
59 * Kernel objects must be located in memory reserved for the kernel. They
63   object. Kernel objects may not be members of a union data type.
65 Kernel objects that are found but do not meet the above conditions will not be
77 Kernel objects may also be allocated at runtime if
95 supervisor threads to acquire permissions on objects they are using even though
105 Any instances of structs or arrays corresponding to kernel objects that meet
107 special perfect hash table of kernel objects generated by the 'gperf' tool.
134 Dynamic objects allocated at runtime are tracked in a runtime red/black tree
155 on its own thread object. Other kernel objects by default are not usable.
167   number of pointers to kernel objects and calls
181   access to a set of kernel objects at boot time.
189 API calls from supervisor mode to set permissions on kernel objects that are
199 Most operations on kernel objects will fail if the object is considered to be
203 Some objects will be implicitly initialized at boot:
205 * Kernel objects that were declared with static initialization macros
209 * Device driver objects are considered initialized after their init function
215 by a user thread. This is very uncommon, typically only for kernel objects that
240 for creating core kernel objects and new driver subsystems.