Lines Matching full:gem

34   a GEM object or anonymous or page-cache pages mapped also into the CPU
36 * ``gpu_vm_bo``: Abstracts the association of a GEM object and
37   a VM. The GEM object maintains a list of gpu_vm_bos, where each gpu_vm_bo
50   gpu_vm or a GEM object. The dma_resv contains an array / list
63 * ``local object``: A GEM object which is only mapped within a
64   single VM. Local GEM objects share the gpu_vm's dma_resv.
65 * ``external object``: a.k.a shared object: A GEM object which may be shared
72 One of the benefits of VM_BIND is that local GEM objects share the gpu_vm's
74 number of local GEM objects, only one lock is needed to make the exec
98   GEM objects.
100   external GEM objects.
104 * The ``gem_object->gpuva_lock`` This lock protects the GEM object's
105   list of gpu_vm_bos. This is usually the same lock as the GEM
120 The GEM object's list of gpu_vm_bos, and the gpu_vm_bo's list of gpu_vmas
122 same as the GEM object's dma_resv, but if the driver
134 Each gpu_vm_bo holds a reference counted pointer to the underlying GEM
136 gpu_vm_bo. When iterating over the GEM object's list of gpu_vm_bos and
172            // The following list iteration needs the Gem object's
174            // gpu_vmas, but since local gem objects share the gpu_vm's
259 option is to just mark the gpu_vm_bos of the evicted gem object with
532 At bind time, assuming a GEM object backed gpu_vma, each
534 gpu_vm_bo in turn needs to be added to the GEM object's
540 the ``gpu_vm->resv`` or the GEM object's dma_resv, that the gpu_vmas
567 zapping. For GEM object backed gpu_vmas, zapping will take place under
568 the GEM object's dma_resv and ensuring that the dma_resv is held also
569 when populating the page-tables for any gpu_vma pointing to the GEM