Re: [Intel-gfx] [PATCH v2 01/11] drm/i915: Create distinct lockclasses for execution vs user timelines

2016-11-08 Thread Chris Wilson
On Tue, Nov 08, 2016 at 09:43:21AM +0200, Joonas Lahtinen wrote: > On ma, 2016-11-07 at 13:59 +, Chris Wilson wrote: > > @@ -56,6 +61,24 @@ int i915_gem_timeline_init(struct drm_i915_private *i915, > >   return 0; > >  } > >   > > +int i915_gem_timeline_init(struct drm_i915_private *i915, >

Re: [Intel-gfx] [PATCH v2 01/11] drm/i915: Create distinct lockclasses for execution vs user timelines

2016-11-07 Thread Joonas Lahtinen
On ma, 2016-11-07 at 13:59 +, Chris Wilson wrote: > @@ -56,6 +61,24 @@ int i915_gem_timeline_init(struct drm_i915_private *i915, >   return 0; >  } >   > +int i915_gem_timeline_init(struct drm_i915_private *i915, > +    struct i915_gem_timeline *timeline, > +

[Intel-gfx] [PATCH v2 01/11] drm/i915: Create distinct lockclasses for execution vs user timelines

2016-11-07 Thread Chris Wilson
In order to simplify the lockdep annotation, as they become more complex in the future with deferred execution and multiple paths through the same functions, create a separate lockclass for the user timeline and the hardware execution timeline. We should only ever be locking the user timeline and