Lines Matching refs:userspace

238 - full transparency for existing users on the importer side, i.e. userspace
347    the need to handle this specially in userspace frameworks for buffer sharing
349    from userspace using mmap.
352    rather similar to dma-buf from a userspace consumer side with using fds as
354    dma-buf to have a good transition path for existing Android userspace.
356    No special interfaces, userspace simply calls mmap on the dma-buf fd.
361    the userspace code of a given importing subsystem can use the same interfaces
363    especially important for drm where the userspace part of contemporary OpenGL,
380    up a mapping in userspace, calling do_mmap with dma_buf->file will equally
390    userspace, the exporter needs to set up a coherent mapping. If that's not
401    for userspace mappings. But the current assumption is that using mmap is
410    interesting ways depending upong the exporter (if userspace starts depending
443   To avoid this problem, userspace must have a way to request O_CLOEXEC
446   userspace control setting of O_CLOEXEC flag passed in to dma_buf_fd().