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
169 often the case in embedded devices. Drivers can create GEM objects with
170 no shmfs backing (called private GEM objects) by initializing them with a call
172 private GEM objects must be managed by drivers.
174 GEM Objects Lifetime
177 All GEM objects are reference-counted by the GEM core. References can be
191 GEM Objects Naming
194 Communication between userspace and the kernel refers to GEM objects
203 associated GEM objects.
211 Handles don't take ownership of GEM objects, they only take a reference
213 avoid leaking GEM objects, drivers must make sure they drop the
223 globally. Names can't be used directly to refer to objects in the DRM
238 GEM Objects Mapping
247 The mmap system call can't be used directly to map GEM objects, as they
249 co-exist to map GEM objects to userspace. The first method uses a
335 objects, and then submit them to GEM. At that point, GEM takes care to
336 bind all the objects into the GTT, execute the buffer, and provide
338 This often involves evicting some objects from the GTT and re-binding
341 to submit command buffers that reference more objects than can fit in
343 Similarly, if several objects in the buffer require fence registers to
526 DRM Sync Objects