drm/i915/gt: Use intel_gt as the primary object for handling resets
Having taken the first step in encapsulating the functionality by moving the related files under gt/, the next step is to start encapsulating by passing around the relevant structs rather than the global drm_i915_private. In this step, we pass intel_gt to intel_reset.c Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com> Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20190712192953.9187-1-chris@chris-wilson.co.uk
This commit is contained in:
@@ -1401,8 +1401,7 @@ long i915_request_wait(struct i915_request *rq,
|
||||
* serialise wait/reset with an explicit lock, we do want
|
||||
* lockdep to detect potential dependency cycles.
|
||||
*/
|
||||
mutex_acquire(&rq->i915->gpu_error.wedge_mutex.dep_map,
|
||||
0, 0, _THIS_IP_);
|
||||
mutex_acquire(&rq->engine->gt->reset.mutex.dep_map, 0, 0, _THIS_IP_);
|
||||
|
||||
/*
|
||||
* Optimistic spin before touching IRQs.
|
||||
@@ -1480,7 +1479,7 @@ long i915_request_wait(struct i915_request *rq,
|
||||
dma_fence_remove_callback(&rq->fence, &wait.cb);
|
||||
|
||||
out:
|
||||
mutex_release(&rq->i915->gpu_error.wedge_mutex.dep_map, 0, _THIS_IP_);
|
||||
mutex_release(&rq->engine->gt->reset.mutex.dep_map, 0, _THIS_IP_);
|
||||
trace_i915_request_wait_end(rq);
|
||||
return timeout;
|
||||
}
|
||||
|
Reference in New Issue
Block a user