Re: [Intel-gfx] [PATCH] drm/i915: Move atomic state free from out of fence release

2017-01-24 Thread Chris Wilson
On Tue, Jan 24, 2017 at 10:39:44AM +0200, Joonas Lahtinen wrote: > On ma, 2017-01-23 at 21:29 +, Chris Wilson wrote: > > @@ -17329,6 +17350,9 @@ void intel_modeset_cleanup(struct drm_device *dev) > >  { > >   struct drm_i915_private *dev_priv = to_i915(dev); > >   > > +

Re: [Intel-gfx] [PATCH] drm/i915: Move atomic state free from out of fence release

2017-01-24 Thread Chris Wilson
On Tue, Jan 24, 2017 at 10:39:44AM +0200, Joonas Lahtinen wrote: > On ma, 2017-01-23 at 21:29 +, Chris Wilson wrote: > > Fences are required to support being released from under an atomic context. > > The drm_atomic_state struct may take a mutex when being released and so > > we cannot drop a

Re: [Intel-gfx] [PATCH] drm/i915: Move atomic state free from out of fence release

2017-01-24 Thread Joonas Lahtinen
On ma, 2017-01-23 at 21:29 +, Chris Wilson wrote: > Fences are required to support being released from under an atomic context. > The drm_atomic_state struct may take a mutex when being released and so > we cannot drop a reference to the drm_atomic_state from the fence release > path directly,

[Intel-gfx] [PATCH] drm/i915: Move atomic state free from out of fence release

2017-01-23 Thread Chris Wilson
Fences are required to support being released from under an atomic context. The drm_atomic_state struct may take a mutex when being released and so we cannot drop a reference to the drm_atomic_state from the fence release path directly, and so we need to defer that unreference to a worker. [