Lines Matching refs:objects

99 GEM is data-agnostic. It manages abstract buffer objects without knowing
140 GEM splits creation of GEM objects and allocation of the memory that
143 GEM objects are represented by an instance of struct :c:type:`struct
145 extend GEM objects with private information and thus create a
172 often the case in embedded devices. Drivers can create GEM objects with
173 no shmfs backing (called private GEM objects) by initializing them with a call
175 private GEM objects must be managed by drivers.
180 All GEM objects are reference-counted by the GEM core. References can be
197 Communication between userspace and the kernel refers to GEM objects
206 associated GEM objects.
214 Handles don't take ownership of GEM objects, they only take a reference
216 avoid leaking GEM objects, drivers must make sure they drop the
226 globally. Names can't be used directly to refer to objects in the DRM
250 The mmap system call can't be used directly to map GEM objects, as they
252 co-exist to map GEM objects to userspace. The first method uses a
338 objects, and then submit them to GEM. At that point, GEM takes care to
339 bind all the objects into the GTT, execute the buffer, and provide
341 This often involves evicting some objects from the GTT and re-binding
344 to submit command buffers that reference more objects than can fit in
346 Similarly, if several objects in the buffer require fence registers to