Lines Matching refs:fences
20 synchronization objects can be either generic, like dma-fences or
31 understanding of dma-fences is required to digest this
38 the GPU and CPU. Memory fences are sometimes referred to as
39 user-fences, userspace-fences or gpu futexes and do not necessarily obey
41 The kernel should thus avoid waiting for memory fences with locks held.
46 a certain mode that disallows completion dma-fences.
72 IOCTL returns. A synchronous VM_BIND takes neither in-fences nor
73 out-fences. Synchronous VM_BIND may block and wait for GPU operations;
94 Since asynchronous VM_BIND operations may use dma-fences embedded in
96 memory fences given as VM_BIND in-fences need to be awaited
97 synchronously before the VM_BIND ioctl returns, since dma-fences,
99 to depend on memory fences that don't have such a restriction.
104 operation is not allowed and any in-fences need to be awaited
106 fences gated by a long-running workload and used as in-syncobjs for the
108 above). Second, any dma-fences used as in-syncobjs for VM_BIND
110 anyway since long-running workloads don't allow for dma-fences as
115 not affect using dma-fences as dependencies for the long-running
137 select memory fences as out-fences since that gives greater flexibility for