Lines Matching refs:user
126 * 6. Add a user interrupt command to the buffer. This command instructs
185 * the object. Simple! ... The relocation entries are stored in user memory
234 * copy the user's batchbuffer to a shadow (so that the user doesn't have
911 * If the user has opted-in for protected-object tracking, make
1517 * do relocations we are already stalling, disable the user's opt
1522 /* and update the user's relocation entry */
1540 * to read. However, if the array is not writable the user loses
1554 * whilst holding the struct mutex lest the user pass in the
1801 * 1 - we try to just prefault all the user relocation entries and
1804 * 2 - we copy the user entries to a local buffer here outside of the
1867 * Leave the user relocations as are, this is the painfully slow path,
1961 * If the user expects the execobject.offset and
2488 * maximum user request size (to avoid blocking) and then backoff.
2547 * that is user interruptable and this clean up step
2920 struct drm_i915_gem_exec_fence __user *user;
2933 ULONG_MAX / sizeof(*user),
2937 user = u64_to_user_ptr(args->cliprects_ptr);
2938 if (!access_ok(user, num_fences * sizeof(*user)))
2954 if (__copy_from_user(&user_fence, user++, sizeof(user_fence)))
3451 * If the user expects the execobject.offset and
3599 /* Copy the new buffer offsets back to the user's exec list. */