diff options
| author | Chris Wilson | 2017-01-27 10:40:08 +0100 |
|---|---|---|
| committer | Chris Wilson | 2017-01-27 20:55:48 +0100 |
| commit | fec0445caa273209d2809760ac7c63e743d6f512 (patch) | |
| tree | 12a465dab8256f388519f0cdd73bdc8e0889b410 /drivers/gpu/drm/i915/intel_ringbuffer.c | |
| parent | drm/i915: Enable userspace to opt-out of implicit fencing (diff) | |
| download | kernel-qcow2-linux-fec0445caa273209d2809760ac7c63e743d6f512.tar.gz kernel-qcow2-linux-fec0445caa273209d2809760ac7c63e743d6f512.tar.xz kernel-qcow2-linux-fec0445caa273209d2809760ac7c63e743d6f512.zip | |
drm/i915: Support explicit fencing for execbuf
Now that the user can opt-out of implicit fencing, we need to give them
back control over the fencing. We employ sync_file to wrap our
drm_i915_gem_request and provide an fd that userspace can merge with
other sync_file fds and pass back to the kernel to wait upon before
future execution.
Testcase: igt/gem_exec_fence
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Acked-by: Chad Versace <chadversary@chromium.org>
Link: http://patchwork.freedesktop.org/patch/msgid/20170127094008.27489-2-chris@chris-wilson.co.uk
Diffstat (limited to 'drivers/gpu/drm/i915/intel_ringbuffer.c')
0 files changed, 0 insertions, 0 deletions