summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/display/dc/dc.h
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2018-05-12 09:49:57 +0100
committerChris Wilson <chris@chris-wilson.co.uk>2018-05-14 11:49:09 +0100
commit0c591a40af1b369cc11dce4d558dd71bebbdc090 (patch)
tree972ef15f48c88c1e1a4a8c29ada1290ed7cf7b95 /drivers/gpu/drm/amd/display/dc/dc.h
parent4db518e4e8286ca93bd5399f26549eafc87607ea (diff)
downloadop-kernel-dev-0c591a40af1b369cc11dce4d558dd71bebbdc090.zip
op-kernel-dev-0c591a40af1b369cc11dce4d558dd71bebbdc090.tar.gz
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
Diffstat (limited to 'drivers/gpu/drm/amd/display/dc/dc.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud