Lines Matching full:objects

54   order. Please refer to the ``Reservation Objects`` section of the
64   single VM. Local GEM objects share the gpu_vm's dma_resv.
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.
150 Revalidation and eviction of local objects
159 With VM_BIND, all local objects need to be resident when the gpu is
160 executing using the gpu_vm, and the objects need to have valid
174            // gpu_vmas, but since local gem objects share the gpu_vm's
199 Eviction of one of these local objects will then look similar to the
221 objects have their dma_resv locked and, due to the above equality, also
238 Locking with external buffer objects
241 Since external buffer objects may be shared by multiple gpu_vm's they
244 objects bound to a gpu_vm using one or many gpu_vmas are therefore put on a
249 objects. However, if instead a list spinlock is used, a more elaborate
262 traversing the list of external objects and locking them. At that time,
327 gpu_vm's evict list and external objects lists. However, there are