diff options
| author | Chris Wilson <chris@chris-wilson.co.uk> | 2017-03-02 15:03:56 +0000 |
|---|---|---|
| committer | Chris Wilson <chris@chris-wilson.co.uk> | 2017-03-02 15:47:19 +0000 |
| commit | f73b567462e0f086bbff5ae22040ff1bc3d87487 (patch) | |
| tree | 5952fbc2b3b09ee96bbfacf7b78660775d95f4c2 /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | 25afdf89ad8c8751be25100b55ee7f09fddaa52e (diff) | |
drm/i915: Include GT/seqno activity in engine/hangcheck debugfs
Whilst investigating some mysterious failures with hangcheck not running
during gem_busy/basic-hang-default, the question is why did we decide to
cancel the retire_work (which queues the hangcheck)? That decision is
based around GT activity, so include that information in the debug
report.
v2: Include the GT awake status in the error state
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20170302150356.9713-1-chris@chris-wilson.co.uk
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions