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)
committerSasha Levin <sasha.levin@oracle.com>
Sat, 28 Mar 2015 13:53:17 +0000 (09:53 -0400)
commit2c7f0370166faf409e67c9bbcb098ed02c78d182
tree82d6f6bfb3aef54798148407b4d05d31cf72ad2c
parentc95800d035abe0ad19aa8352e64c237e10724e67
drm/vmwgfx: Fix a couple of lock dependency violations

[ Upstream commit 5151adb37a5918957f4c33a8d8e7629c0fb00563 ]

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>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c