Lines Matching refs:userspace

29  * Only use fixed sized integers. To avoid conflicts with typedefs in userspace
42  * Pointers are __u64, cast from/to a uintprt_t on the userspace side and
56  * Have a clear way for userspace to figure out whether your new ioctl or ioctl
63    and zero-extends any mismatches between kernel and userspace. That helps,
64    but isn't a complete solution since newer userspace on older kernels won't
106    userspace library. The i915 driver botched this with the set_tiling ioctl,
108    userspace.
130    v4l use by default nowadays. But let userspace know which timestamps are
134    have this information they can at least compensate. If your userspace can
167 for different objects and other resources to userspace. Doing that right
173    also simplifies lifetime management for userspace.
186  * Think about uniqueness requirements for userspace handles. E.g. for most drm
187    drivers it's a userspace bug to submit the same object twice in the same
188    command submission ioctl. But then if objects are shareable userspace needs