drm/i915: Mark up nested spinlocks
authorChris Wilson <chris@chris-wilson.co.uk>
Sat, 12 May 2018 08:49:57 +0000 (09:49 +0100)
committerChris Wilson <chris@chris-wilson.co.uk>
Mon, 14 May 2018 10:49:09 +0000 (11:49 +0100)
commit0c591a40af1b369cc11dce4d558dd71bebbdc090
tree972ef15f48c88c1e1a4a8c29ada1290ed7cf7b95
parent4db518e4e8286ca93bd5399f26549eafc87607ea
drm/i915: Mark up nested spinlocks

When we process the outstanding requests upon banning a context, we need
to acquire both the engine and the client's timeline, nesting the locks.
This requires explicit markup as the two timelines are now of the same
class, since commit a89d1f921c15 ("drm/i915: Split i915_gem_timeline into
individual timelines").

Testcase: igt/gem_eio/banned
Fixes: a89d1f921c15 ("drm/i915: Split i915_gem_timeline into individual timelines")
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Michel Thierry <michel.thierry@intel.com>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20180512084957.9829-1-chris@chris-wilson.co.uk
drivers/gpu/drm/i915/i915_gem.c