Files
linux/drivers
Chris Wilson 07779a76ee drm/i915: Mark up the calling context for intel_wakeref_put()
Previously, we assumed we could use mutex_trylock() within an atomic
context, falling back to a worker if contended. However, such trickery
is illegal inside interrupt context, and so we need to always use a
worker under such circumstances. As we normally are in process context,
we can typically use a plain mutex, and only defer to a work when we
know we are being called from an interrupt path.

Fixes: 51fbd8de87 ("drm/i915/pmu: Atomically acquire the gt_pm wakeref")
References: a0855d24fc ("locking/mutex: Complain upon mutex API misuse in IRQ contexts")
References: https://bugs.freedesktop.org/show_bug.cgi?id=111626
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20191120125433.3767149-1-chris@chris-wilson.co.uk
2019-11-20 15:59:23 +00:00
..
2019-08-27 09:43:59 +02:00
2019-08-16 11:33:56 -07:00
2019-10-27 15:57:19 +00:00
2019-10-23 12:10:05 +02:00
2019-10-23 12:10:05 +02:00
2019-11-06 21:48:29 -08:00
2019-09-23 17:20:40 -04:00
2019-10-15 23:51:36 +02:00
2019-10-22 17:55:51 +02:00
2019-08-18 12:56:10 +02:00
2019-10-26 19:47:31 +08:00
2019-10-15 14:07:01 -06:00
2019-11-14 05:53:10 +10:00