diff options
| author | Chris Wilson <[email protected]> | 2018-04-28 12:15:32 +0100 |
|---|---|---|
| committer | Chris Wilson <[email protected]> | 2018-04-30 11:52:41 +0100 |
| commit | 5692251c254a3d561316c4e8e10c77e470b60658 (patch) | |
| tree | e95f4a56262274a50cb182ad1b987849e34520b1 /tools/perf/scripts/python/syscall-counts.py | |
| parent | 78b60ce7b96cf1869b51cee916a40041e400d6ce (diff) | |
drm/i915/lrc: Scrub the GPU state of the guilty hanging request
Previously, we just reset the ring register in the context image such
that we could skip over the broken batch and emit the closing
breadcrumb. However, on resume the context image and GPU state would be
reloaded, which may have been left in an inconsistent state by the
reset. The presumption was that at worst it would just cause another
reset and skip again until it recovered, however it seems just as likely
to cause an unrecoverable hang. Instead of risking loading an incomplete
context image, restore it back to the default state.
v2: Fix up off-by-one from including the ppHSWP in with the register
state.
v3: Use a ring local to compact a few lines.
v4: Beware setting the ring local before checking for a NULL request.
References: https://bugs.freedesktop.org/show_bug.cgi?id=105304
Signed-off-by: Chris Wilson <[email protected]>
Cc: Mika Kuoppala <[email protected]>
Cc: MichaĆ Winiarski <[email protected]>
Cc: Michel Thierry <[email protected]>
Cc: Tvrtko Ursulin <[email protected]>
Reviewed-by: Michel Thierry <[email protected]> #v2
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions