Lines Matching refs:fences

134    :doc: DMA fences overview
187 * Future fences, used in HWC1 to signal when a buffer isn't used by the display
191 * Proxy fences, proposed to handle &drm_syncobj for which the fence has not yet
194 * Userspace fences or gpu futexes, fine-grained locking within a command buffer
200   batch DMA fences for memory management instead of context preemption DMA
201   fences which get reattached when the compute job is rescheduled.
204 fences and controls when they fire. Mixing indefinite fences with normal
205 in-kernel DMA fences does not work, even when a fallback timeout is included to
211 * Only userspace knows about all dependencies in indefinite fences and when
215 for memory management needs, which means we must support indefinite fences being
216 dependent upon DMA fences. If the kernel also support indefinite fences in the
227       userspace [label="userspace controlled fences"]
242 fences in the kernel. This means:
244 * No future fences, proxy fences or userspace fences imported as DMA fences,
247 * No DMA fences that signal end of batchbuffer for command submission where