Lines Matching full:userspace

16  - dma-buf, representing a sg_table and exposed to userspace as a file
26 Userspace API principles and use
30 see Documentation/userspace-api/dma-buf-alloc-exchange.rst.
68 Userspace Interface Notes
71 Mostly a DMA buffer file descriptor is simply an opaque object for userspace,
81 cases. Userspace can use this to detect support for discovering the dma-buf
96 To avoid this problem, userspace must have a way to request O_CLOEXEC
99 userspace control setting of O_CLOEXEC flag passed in to dma_buf_fd().
245 The time this fence completes is entirely under userspace's control.
250 * Userspace fences or gpu futexes, fine-grained locking within a command buffer
251 that userspace uses for synchronization across engines or with the CPU, which
259 Common to all these schemes is that userspace controls the dependencies of these
262 protect against malicious userspace:
264 * Only the kernel knows about all DMA fence dependencies, userspace is not aware
267 * Only userspace knows about all dependencies in indefinite fences and when
270 Furthermore the kernel has to be able to hold up userspace command submission
283 userspace [label="userspace controlled fences"]
284 kernel -> userspace [label="memory management"]
285 userspace -> kernel [label="Future fence, fence proxy, ..."]
287 { rank=same; kernel userspace }
291 through memory management dependencies which userspace is unaware of, which
293 userspace's perspective, do not contain a deadlock. In such a mixed fencing
300 * No future fences, proxy fences or userspace fences imported as DMA fences,
304 userspace is allowed to use userspace fencing or long running compute
318 synchronization. Synchronization fences controlled by userspace must be used
322 Linux rely on DMA fences, which means without an entirely new userspace stack
323 built on top of userspace fences, they cannot benefit from recoverable page
380 problem is new, because some other CPU thread in userspace might
381 hit a page fault which holds up a userspace fence - supporting page faults on