summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorMatt Roper <matthew.d.roper@intel.com>2023-03-27 22:55:47 +0300
committerAndi Shyti <andi.shyti@linux.intel.com>2023-03-28 12:22:06 +0300
commitfdd9b7dcf1ad7115b2d997e047e8e978c474736b (patch)
treed61f88b4e16faae1a0a91483d6454b43b805ea46 /tools/perf/scripts/python/stackcollapse.py
parentde4149730d9d72f50d4e6dfedad0d11b1df05b7e (diff)
downloadlinux-fdd9b7dcf1ad7115b2d997e047e8e978c474736b.tar.xz
drm/i915: Check for unreliable MMIO during forcewake
Although we now sanitycheck MMIO access during driver load to make sure the MMIO BAR isn't returning all 0xFFFFFFFF, there have been a few cases where (temporarily?) unreliable MMIO access has happened after GPU resets or power events. We'll often notice this on our next GT register access since forcewake handling will fail; let's change our handling slightly so that when this happens we print a more meaningful message clarifying that the problem is the MMIO access, not forcewake specifically. Signed-off-by: Matt Roper <matthew.d.roper@intel.com> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com> Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com> Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20230327195547.356584-3-andi.shyti@linux.intel.com
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions