Re: [Intel-gfx] [PATCH 12/29] drm/armada: Drop struct_mutex from cursor paths

2015-12-03 Thread Daniel Vetter
On Thu, Dec 03, 2015 at 04:08:45PM +, Russell King - ARM Linux wrote: > On Mon, Nov 23, 2015 at 10:32:45AM +0100, Daniel Vetter wrote: > > @@ -957,11 +955,9 @@ static int armada_drm_crtc_cursor_move(struct drm_crtc > > *crtc, int x, int y) > > if (!dcrtc->variant->has_spu_adv_reg) > >

Re: [Intel-gfx] [PATCH 12/29] drm/armada: Drop struct_mutex from cursor paths

2015-12-03 Thread Russell King - ARM Linux
On Mon, Nov 23, 2015 at 10:32:45AM +0100, Daniel Vetter wrote: > @@ -957,11 +955,9 @@ static int armada_drm_crtc_cursor_move(struct drm_crtc > *crtc, int x, int y) > if (!dcrtc->variant->has_spu_adv_reg) > return -EFAULT; > > - mutex_lock(>struct_mutex); >

[Intel-gfx] [PATCH 12/29] drm/armada: Drop struct_mutex from cursor paths

2015-11-23 Thread Daniel Vetter
The kms state itself is already protected by the modeset locks acquired by the drm core. The only thing left is gem bo state, and since the cursor code expects small objects which are statically mapped at create time and then invariant over the lifetime of the gem bo there's nothing to protect.