drm/i915: Refactor export_fence() after i915_vma_move_to_active()

Browse source

Currently all callers are responsible for adding the vma to the active
timeline and then exporting its fence. Combine the two operations into
i915_vma_move_to_active() to move all the extra handling from the
callers to the single site.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20180706103947.15919-1-chris@chris-wilson.co.uk

...

This commit is contained in:

Chris Wilson 2018-07-06 11:39:42 +01:00

parent 8fdbfd8686

commit da99fe5f85

6 changed files with 21 additions and 45 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

47

drivers/gpu/drm/i915/i915_gem_execbuffer.c

View file

4

drivers/gpu/drm/i915/selftests/huge_pages.c

View file

4

drivers/gpu/drm/i915/selftests/i915_gem_coherency.c

View file

4

drivers/gpu/drm/i915/selftests/i915_gem_context.c

View file

4

drivers/gpu/drm/i915/selftests/i915_gem_object.c

View file

3

drivers/gpu/drm/i915/selftests/intel_workarounds.c

View file