drm/i915: Apply a cond_resched() to the saturated signaler
authorChris Wilson <chris@chris-wilson.co.uk>
Tue, 4 Apr 2017 12:05:31 +0000 (13:05 +0100)
committerJani Nikula <jani.nikula@intel.com>
Wed, 26 Apr 2017 13:27:58 +0000 (16:27 +0300)
commitd445aaaac0879a4c4400bf59f20465ba3e8445f1
tree6e53e03eeb20182f7d9cbb307ccc992e5146d3ee
parent1676a2b35cd5a548da17d1106fb0d4d238c0d191
drm/i915: Apply a cond_resched() to the saturated signaler

If the engine is continually completing nops, we can saturate the
signaler and keep it working indefinitely. This angers the NMI watchdog!

A good example is to disable semaphores on snb and run igt/gem_exec_nop -
the parallel, multi-engine workloads are more than sufficient to hog the
CPU, preventing the system from even processing ICMP echo replies.

v2: Tvrtko dug into cond_resched() on x86 and found that it only
depended upon preempt_count and not tif_need_resched() - which means
that we would always call schedule() at that point.

Fixes: c81d46138da6 ("drm/i915: Convert trace-irq to the breadcrumb waiter")
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@intel.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20170404120531.10737-1-chris@chris-wilson.co.uk
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
(cherry picked from commit a7980a640cbd339aa80f406d1786a275a2c320bc)
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
drivers/gpu/drm/i915/intel_breadcrumbs.c