diff options
| author |   Chris Wilson <chris@chris-wilson.co.uk> | 2018-03-07 13:42:26 +0000 |
|---|---|---|
| committer |   Joonas Lahtinen <joonas.lahtinen@linux.intel.com> | 2018-03-16 14:35:35 +0200 |
| commit | 73e2232aa3253d77935112bfc218700f6a2f1000 (patch) | |
| tree | e7cd5ca947a0e1df1bd4e1ef8abdb794945a2e3c /lib/test_overflow.c | |
| parent | drm/i915: Wrap engine->schedule in RCU locks for set-wedge protection (diff) | |
| download | linux-dev-73e2232aa3253d77935112bfc218700f6a2f1000.tar.xz linux-dev-73e2232aa3253d77935112bfc218700f6a2f1000.zip | |
drm/i915: Only call tasklet_kill() on the first prepare_reset
tasklet_kill() will spin waiting for the current tasklet to be executed.
However, if tasklet_disable() has been called, then the tasklet is never
executed but permanently put back onto the runlist until
tasklet_enable() is called. Ergo, we cannot use tasklet_kill() inside a
disable/enable pair. This is the case when we call set-wedge from inside
i915_reset(), and another request was submitted to us concurrent to the
reset.
Fixes: 963ddd63c314 ("drm/i915: Suspend submission tasklets around wedging")
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20180307134226.25492-6-chris@chris-wilson.co.uk
(cherry picked from commit 68ad361285a9cc73b259f59adbaafde196c15987)
Signed-off-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Diffstat (limited to 'lib/test_overflow.c')
0 files changed, 0 insertions, 0 deletions