Lines Matching full:objects

96 GEM is data-agnostic. It manages abstract buffer objects without knowing
134 GEM Objects Creation
137 GEM splits creation of GEM objects and allocation of the memory that
140 GEM objects are represented by an instance of struct :c:type:`struct
142 extend GEM objects with private information and thus create a
174 often the case in embedded devices. Drivers can create GEM objects with
175 no shmfs backing (called private GEM objects) by initializing them with a call
177 private GEM objects must be managed by drivers.
179 GEM Objects Lifetime
182 All GEM objects are reference-counted by the GEM core. References can be
196 GEM Objects Naming
199 Communication between userspace and the kernel refers to GEM objects
208 associated GEM objects.
216 Handles don't take ownership of GEM objects, they only take a reference
218 avoid leaking GEM objects, drivers must make sure they drop the
228 globally. Names can't be used directly to refer to objects in the DRM
243 GEM Objects Mapping
252 The mmap system call can't be used directly to map GEM objects, as they
254 co-exist to map GEM objects to userspace. The first method uses a
312 objects is handled by providing a custom get_unmapped_area file
352 objects, and then submit them to GEM. At that point, GEM takes care to
353 bind all the objects into the GTT, execute the buffer, and provide
355 This often involves evicting some objects from the GTT and re-binding
358 to submit command buffers that reference more objects than can fit in
360 Similarly, if several objects in the buffer require fence registers to
549 DRM Sync Objects