diff options
| author | Daniel Vetter <daniel.vetter@ffwll.ch> | 2011-11-27 18:58:17 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-02-13 11:06:09 -0800 |
| commit | 5b19005c6230e6a65d3fe3de8f514feac7d2eebb (patch) | |
| tree | d71de66a187a3484610face07d834e1e997a7436 /lib/plist.c | |
| parent | 1f8991ccf771442ae2423971798a6ca9d6db6343 (diff) | |
| download | kernel_samsung_espresso10-5b19005c6230e6a65d3fe3de8f514feac7d2eebb.zip kernel_samsung_espresso10-5b19005c6230e6a65d3fe3de8f514feac7d2eebb.tar.gz kernel_samsung_espresso10-5b19005c6230e6a65d3fe3de8f514feac7d2eebb.tar.bz2 | |
drm/i915: check ACTHD of all rings
commit 097354eb14fa94d31a09c64d640643f58e4a5a9a upstream.
Otherwise hangcheck spuriously fires when running blitter/bsd-only
workloads.
Contrary to a similar patch by Ben Widawsky this does not check
INSTDONE of the other rings. Chris Wilson implied that in a failure to
detect a hang, most likely because INSTDONE was fluctuating. Thus only
check ACTHD, which as far as I know is rather reliable. Also, blitter
and bsd rings can't launch complex tasks from a single instruction
(like 3D_PRIM on the render with complex or even infinite shaders).
This fixes spurious gpu hang detection when running
tests/gem_hangcheck_forcewake on snb/ivb.
Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Keith Packard <keithp@keithp.com>
Signed-off-by: Eugeni Dodonov <eugeni.dodonov@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'lib/plist.c')
0 files changed, 0 insertions, 0 deletions