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
This commit is contained in:
@@ -110,8 +110,7 @@ __live_active_setup(struct drm_i915_private *i915)
|
||||
submit,
|
||||
GFP_KERNEL);
|
||||
if (err >= 0)
|
||||
err = i915_active_ref(&active->base,
|
||||
rq->fence.context, rq);
|
||||
err = i915_active_ref(&active->base, rq->timeline, rq);
|
||||
i915_request_add(rq);
|
||||
if (err) {
|
||||
pr_err("Failed to track active ref!\n");
|
||||
|
Reference in New Issue
Block a user