Lines Matching full:objects

65 - We prevent use of device drivers or kernel objects not specifically granted,
80   - Use of kernel objects that are not in a proper initialization state.
105   logic for creating the tables of valid kernel objects, defining system calls,
111   for kernel objects should always be configured as supervisor-only.
114   assign them permissions to kernel objects. In general, all C and header
142   domains, or via kernel objects such as semaphores and pipes.
144 - User threads cannot directly access memory belonging to kernel objects.
145   Although pointers to kernel objects are used to reference them, actual
146   manipulation of kernel objects is done through system call interfaces. Device
147   drivers and threads stacks are also considered kernel objects. This ensures
156   permissions of all kernel objects granted to the parent, except the parent
174 All kernel objects, thread stacks, and device driver instances must be defined
176 kernel objects will need to go through pre-defined pools of available objects.
181 - Loaded object code will not be able to define any kernel objects that will be
183   requesting kernel objects from pools.