drm/i915: Markup expected timeline locks for i915_active
As every i915_active_request should be serialised by a dedicated lock, i915_active consists of a tree of locks; one for each node. Markup up the i915_active_request with what lock is supposed to be guarding it so that we can verify that the serialised updated are indeed serialised. Signed-off-by:Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by:
Mika Kuoppala <mika.kuoppala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20190816121000.8507-2-chris@chris-wilson.co.uk
Showing
- drivers/gpu/drm/i915/display/intel_overlay.c 1 addition, 1 deletiondrivers/gpu/drm/i915/display/intel_overlay.c
- drivers/gpu/drm/i915/gem/i915_gem_client_blt.c 1 addition, 1 deletiondrivers/gpu/drm/i915/gem/i915_gem_client_blt.c
- drivers/gpu/drm/i915/gem/i915_gem_context.c 1 addition, 1 deletiondrivers/gpu/drm/i915/gem/i915_gem_context.c
- drivers/gpu/drm/i915/gt/intel_context.c 3 additions, 8 deletionsdrivers/gpu/drm/i915/gt/intel_context.c
- drivers/gpu/drm/i915/gt/intel_engine_pool.h 1 addition, 1 deletiondrivers/gpu/drm/i915/gt/intel_engine_pool.h
- drivers/gpu/drm/i915/gt/intel_timeline.c 3 additions, 4 deletionsdrivers/gpu/drm/i915/gt/intel_timeline.c
- drivers/gpu/drm/i915/gt/selftest_timeline.c 4 additions, 0 deletionsdrivers/gpu/drm/i915/gt/selftest_timeline.c
- drivers/gpu/drm/i915/gt/selftests/mock_timeline.c 1 addition, 1 deletiondrivers/gpu/drm/i915/gt/selftests/mock_timeline.c
- drivers/gpu/drm/i915/i915_active.c 15 additions, 4 deletionsdrivers/gpu/drm/i915/i915_active.c
- drivers/gpu/drm/i915/i915_active.h 10 additions, 2 deletionsdrivers/gpu/drm/i915/i915_active.h
- drivers/gpu/drm/i915/i915_active_types.h 15 additions, 0 deletionsdrivers/gpu/drm/i915/i915_active_types.h
- drivers/gpu/drm/i915/i915_vma.c 2 additions, 2 deletionsdrivers/gpu/drm/i915/i915_vma.c
- drivers/gpu/drm/i915/selftests/i915_active.c 1 addition, 2 deletionsdrivers/gpu/drm/i915/selftests/i915_active.c
Loading
Please register or sign in to comment