Files
linux/drivers/gpu/drm
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-11-14 05:53:10 +10:00
2019-08-14 18:31:10 +02:00
2019-11-14 05:53:10 +10:00
2019-10-24 17:59:45 +02:00
2019-10-04 17:04:05 +01:00
2019-10-03 16:38:50 +02:00
2019-06-30 09:48:05 +02:00
2019-11-13 15:34:15 -05:00
2019-10-23 12:10:05 +02:00
2019-11-14 05:53:10 +10:00
2019-07-17 12:52:55 +02:00
2019-11-14 05:53:10 +10:00
2019-06-05 20:31:04 +02:00
2019-07-15 18:11:31 +02:00
2019-06-05 20:29:57 +02:00
2019-09-16 15:14:43 +02:00
2019-07-17 12:52:55 +02:00
2019-11-14 05:53:10 +10:00
2019-10-23 11:14:11 -04:00
2019-07-22 21:24:10 +02:00
2019-05-27 18:07:03 +02:00
2019-05-27 18:07:03 +02:00
2019-10-08 18:29:00 +02:00
2019-05-27 18:07:03 +02:00
2019-05-27 18:07:03 +02:00
2019-07-22 21:24:10 +02:00
2019-05-27 18:07:03 +02:00
2019-06-19 12:07:29 +02:00
2019-05-27 18:07:03 +02:00
2019-10-02 16:28:55 +03:00
2019-05-27 18:07:03 +02:00
2019-10-03 16:38:50 +02:00