b2dbf8d982
As we have already plugged the w->dma into the reservation_object, and have set ourselves up to automatically signal the request and w->dma on completion, we do not need to export the rq->fence directly and just use the w->dma fence. This avoids having to take the reservation_lock inside the worker which cross-release lockdep would complain about. :) Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Matthew Auld <matthew.auld@intel.com> Reviewed-by: Matthew Auld <matthew.auld@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20190621215733.12070-1-chris@chris-wilson.co.uk |
||
---|---|---|
.. | ||
huge_gem_object.c | ||
huge_gem_object.h | ||
huge_pages.c | ||
i915_gem_client_blt.c | ||
i915_gem_coherency.c | ||
i915_gem_context.c | ||
i915_gem_dmabuf.c | ||
i915_gem_mman.c | ||
i915_gem_object_blt.c | ||
i915_gem_object.c | ||
i915_gem_phys.c | ||
igt_gem_utils.c | ||
igt_gem_utils.h | ||
mock_context.c | ||
mock_context.h | ||
mock_dmabuf.c | ||
mock_dmabuf.h | ||
mock_gem_object.h |