Lines Matching full:userspace

12 sg_table and exposed to userspace as a file descriptor to allow passing
52 Userspace Interface Notes
55 Mostly a DMA buffer file descriptor is simply an opaque object for userspace,
65   cases. Userspace can use this to detect support for discovering the dma-buf
80   To avoid this problem, userspace must have a way to request O_CLOEXEC
83   userspace control setting of O_CLOEXEC flag passed in to dma_buf_fd().
211   The time this fence completes is entirely under userspace's control.
216 * Userspace fences or gpu futexes, fine-grained locking within a command buffer
217   that userspace uses for synchronization across engines or with the CPU, which
225 Common to all these schemes is that userspace controls the dependencies of these
228 protect against malicious userspace:
230 * Only the kernel knows about all DMA fence dependencies, userspace is not aware
233 * Only userspace knows about all dependencies in indefinite fences and when
236 Furthermore the kernel has to be able to hold up userspace command submission
249       userspace [label="userspace controlled fences"]
250       kernel -> userspace [label="memory management"]
251       userspace -> kernel [label="Future fence, fence proxy, ..."]
253       { rank=same; kernel userspace }
257 through memory management dependencies which userspace is unaware of, which
259 userspace's perspective, do not contain a deadlock.  In such a mixed fencing
266 * No future fences, proxy fences or userspace fences imported as DMA fences,
270   userspace is allowed to use userspace fencing or long running compute
284 synchronization. Synchronization fences controlled by userspace must be used
288 Linux rely on DMA fences, which means without an entirely new userspace stack
289 built on top of userspace fences, they cannot benefit from recoverable page
346 problem is new, because some other CPU thread in userspace might
347 hit a page fault which holds up a userspace fence - supporting page faults on