summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorJohn Harrison <John.C.Harrison@Intel.com>2023-11-14 04:00:15 +0300
committerJohn Harrison <John.C.Harrison@Intel.com>2023-12-01 00:50:49 +0300
commitb7d2a4da38fb558832b70c6f45929649a9d114a3 (patch)
tree823801fb3bd194694cc19f60f936dfe8bfc623ec /tools/perf/scripts/python/exported-sql-viewer.py
parent698e19da2914a0021a088b2b5d101d1854862315 (diff)
downloadlinux-b7d2a4da38fb558832b70c6f45929649a9d114a3.tar.xz
drm/i915/guc: Fix for potential false positives in GuC hang selftest
Noticed that the hangcheck selftest is submitting a non-preemptoble spinner. That means that even if the GuC does not die, the heartbeat will still kick in and trigger a reset. Which is rather defeating the purpose of the test - to verify that the heartbeat will kick in if the GuC itself has died. The test is deliberately killing the GuC, so it should never hit the case of a non-dead GuC. But it is not impossible that the kill might fail at some future point due to other driver re-work. So, make the spinner pre-emptible. That way the heartbeat can get through if the GuC is alive and context switching. Thus a reset only happens if the GuC dies. Thus, if the kill should stop working the test will now fail rather than claim to pass. Signed-off-by: John Harrison <John.C.Harrison@Intel.com> Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20231114010016.234570-2-John.C.Harrison@Intel.com
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions