Lines Matching refs:fences
156 :doc: DMA fences overview
212 * Future fences, used in HWC1 to signal when a buffer isn't used by the display
216 * Proxy fences, proposed to handle &drm_syncobj for which the fence has not yet
219 * Userspace fences or gpu futexes, fine-grained locking within a command buffer
225 batch DMA fences for memory management instead of context preemption DMA
226 fences which get reattached when the compute job is rescheduled.
229 fences and controls when they fire. Mixing indefinite fences with normal
230 in-kernel DMA fences does not work, even when a fallback timeout is included to
236 * Only userspace knows about all dependencies in indefinite fences and when
240 for memory management needs, which means we must support indefinite fences being
241 dependent upon DMA fences. If the kernel also support indefinite fences in the
252 userspace [label="userspace controlled fences"]
267 fences in the kernel. This means:
269 * No future fences, proxy fences or userspace fences imported as DMA fences,
272 * No DMA fences that signal end of batchbuffer for command submission where
281 implications for DMA fences.
285 But memory allocations are not allowed to gate completion of DMA fences, which
286 means any workload using recoverable page faults cannot use DMA fences for
287 synchronization. Synchronization fences controlled by userspace must be used
291 Linux rely on DMA fences, which means without an entirely new userspace stack
292 built on top of userspace fences, they cannot benefit from recoverable page
327 requiring DMA fences or jobs requiring page fault handling: This means all DMA
328 fences must complete before a compute job with page fault handling can be
336 fences. This results very wide impact on the kernel, since resolving the page
342 GPUs do not have any impact. This allows us to keep using DMA fences internally
347 Fences` discussions: Infinite fences from compute workloads are allowed to
348 depend on DMA fences, but not the other way around. And not even the page fault