aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/net_dropmonitor.py
diff options
context:
space:
mode:
authorDaniele Ceraolo Spurio <[email protected]>2018-02-07 13:24:40 -0800
committerChris Wilson <[email protected]>2018-02-08 07:34:32 +0000
commitce1599a40da20b0e5e4175fe3ef647d2862cbf41 (patch)
tree6d08c3d5318b0ee86fa34c4b3c26412f9ba00917 /tools/perf/scripts/python/net_dropmonitor.py
parentd63763749127b483ba042b2939ba39fd79792330 (diff)
drm/i915: do not stop engines on sanitize if i915.reset=0
Since commit 5896a5c8c9c0 (drm/i915: Always stop the rings before a missing GPU reset) we attempt to stop the engines during gem_sanitize even if reset=0 and nothing bad happened on the gpu. The specs says that the STOP_RINGS bit needs to be cleared to resume normal operation, but for some reason the value of the bit seems to be changing without us writing to it (maybe rc6 entry/exit?), so normal operation resumes correctly. However, it still feels incorrect to stop the engines if there hasn't been any issue so skip the whole reset call in gem_sanitize if i915.reset=0 Cc: Chris Wilson <[email protected]> Cc: Mika Kuoppala <[email protected]> Signed-off-by: Daniele Ceraolo Spurio <[email protected]> Link: https://patchwork.freedesktop.org/patch/msgid/[email protected] Reviewed-by: Chris Wilson <[email protected]> Signed-off-by: Chris Wilson <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions