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:
@@ -211,7 +211,7 @@ static void clear_pages_worker(struct work_struct *work)
|
||||
* keep track of the GPU activity within this vma/request, and
|
||||
* propagate the signal from the request to w->dma.
|
||||
*/
|
||||
err = i915_active_ref(&vma->active, rq->fence.context, rq);
|
||||
err = i915_active_ref(&vma->active, rq->timeline, rq);
|
||||
if (err)
|
||||
goto out_request;
|
||||
|
||||
|
@@ -908,7 +908,7 @@ static int context_barrier_task(struct i915_gem_context *ctx,
|
||||
if (emit)
|
||||
err = emit(rq, data);
|
||||
if (err == 0)
|
||||
err = i915_active_ref(&cb->base, rq->fence.context, rq);
|
||||
err = i915_active_ref(&cb->base, rq->timeline, rq);
|
||||
|
||||
i915_request_add(rq);
|
||||
if (err)
|
||||
|
Viittaa uudesa ongelmassa
Block a user