drm/vmwgfx: Fix a couple of lock dependency violations
authorThomas Hellstrom <thellstrom@vmware.com>
Mon, 9 Mar 2015 08:56:21 +0000 (01:56 -0700)
committerThomas Hellstrom <thellstrom@vmware.com>
Wed, 11 Mar 2015 18:47:40 +0000 (11:47 -0700)
commit5151adb37a5918957f4c33a8d8e7629c0fb00563
tree87e77a5f2a83a227321a492e3115fa38dc76f487
parentcd961bb9eebb630452f49dcbf3e5f0059428614a
drm/vmwgfx: Fix a couple of lock dependency violations

Experimental lockdep annotation added to the TTM lock has unveiled a
couple of lock dependency violations in the vmwgfx driver. In both
cases it turns out that the device_private::reservation_sem is not
needed so the offending code is moved out of that lock.

Cc: <stable@vger.kernel.org>
Acked-by: Sinclair Yeh <syeh@vmware.com>
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c