drm/i915: Assert that fence->lock is held in an irq-safe manner
authorChris Wilson <chris@chris-wilson.co.uk>
Thu, 2 Mar 2017 11:51:30 +0000 (11:51 +0000)
committerChris Wilson <chris@chris-wilson.co.uk>
Thu, 2 Mar 2017 15:18:55 +0000 (15:18 +0000)
commite60a870d7f83517e583e6094ff5646d3a8d732db
treef861564b3a7f5ffb353abbb0a281ff352d1d1914
parenta5509abda48ecfc133fac6268e83fc1a93dba039
drm/i915: Assert that fence->lock is held in an irq-safe manner

Everytime we take the fence->lock (aka request->lock), we must do so
with irqs disabled since it may be used from within an hardirq context.
As sometimes we are taking the lock in a nested manner, assert that the
caller did disable the irqs for us.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20170302115130.28434-1-chris@chris-wilson.co.uk
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
drivers/gpu/drm/i915/i915_gem_request.c
drivers/gpu/drm/i915/intel_breadcrumbs.c