drm/i915: Consolidate the timeline->barrier
The timeline is strictly ordered, so by inserting the timeline->barrier request into the timeline->last_request it naturally provides the same barrier. Consolidate the pair of barriers into one as they serve the same purpose. 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/20190408091728.20207-4-chris@chris-wilson.co.uk
This commit is contained in:
@@ -253,7 +253,6 @@ int i915_timeline_init(struct drm_i915_private *i915,
|
||||
spin_lock_init(&timeline->lock);
|
||||
mutex_init(&timeline->mutex);
|
||||
|
||||
INIT_ACTIVE_REQUEST(&timeline->barrier);
|
||||
INIT_ACTIVE_REQUEST(&timeline->last_request);
|
||||
INIT_LIST_HEAD(&timeline->requests);
|
||||
|
||||
@@ -326,7 +325,6 @@ void i915_timeline_fini(struct i915_timeline *timeline)
|
||||
{
|
||||
GEM_BUG_ON(timeline->pin_count);
|
||||
GEM_BUG_ON(!list_empty(&timeline->requests));
|
||||
GEM_BUG_ON(i915_active_request_isset(&timeline->barrier));
|
||||
|
||||
i915_syncmap_free(&timeline->sync);
|
||||
|
||||
|
Reference in New Issue
Block a user