Lines Matching refs:userspace

12 sg_table and exposed to userspace as a file descriptor to allow passing
55 Mostly a DMA buffer file descriptor is simply an opaque object for userspace,
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().
189   The time this fence completes is entirely under userspace's control.
195   that userspace uses for synchronization across engines or with the CPU, which
203 Common to all these schemes is that userspace controls the dependencies of these
206 protect against malicious userspace:
208 * Only the kernel knows about all DMA fence dependencies, userspace is not aware
211 * Only userspace knows about all dependencies in indefinite fences and when
214 Furthermore the kernel has to be able to hold up userspace command submission
227       userspace [label="userspace controlled fences"]
228       kernel -> userspace [label="memory management"]
229       userspace -> kernel [label="Future fence, fence proxy, ..."]
231       { rank=same; kernel userspace }
235 through memory management dependencies which userspace is unaware of, which
237 userspace's perspective, do not contain a deadlock.  In such a mixed fencing
244 * No future fences, proxy fences or userspace fences imported as DMA fences,
248   userspace is allowed to use userspace fencing or long running compute