diff options
author | Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com> | 2021-09-03 17:28:37 +0300 |
---|---|---|
committer | Matt Roper <matthew.d.roper@intel.com> | 2021-09-15 17:57:06 +0300 |
commit | dc34ca9231f2631e635a4737242bc0f7fe5c4a45 (patch) | |
tree | 50ab972e1f22cf248398fff2254e9a80e1a18b7a /tools/perf/scripts/python/export-to-sqlite.py | |
parent | ce079f6d87ccd7129675c48067dd49329a123ce6 (diff) | |
download | linux-dc34ca9231f2631e635a4737242bc0f7fe5c4a45.tar.xz |
drm/i915: Mark GPU wedging on driver unregister unrecoverable
GPU wedged flag now set on driver unregister to prevent from further
using the GPU can be then cleared unintentionally when calling
__intel_gt_unset_wedged() still before the flag is finally marked
unrecoverable. We need to have it marked unrecoverable earlier.
Implement that by replacing a call to intel_gt_set_wedged() in
intel_gt_driver_unregister() with intel_gt_set_wedged_on_fini().
With the above in place, intel_gt_set_wedged_on_fini() is now called
twice on driver remove, second time from __intel_gt_disable(). This
seems harmless, while dropping intel_gt_set_wedged_on_fini() from
__intel_gt_disable() proved to break some driver probe error unwind
paths as well as mock selftest exit path.
Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Cc: Michał Winiarski <michal.winiarski@intel.com>
Reviewed-by: Michał Winiarski <michal.winiarski@intel.com>
Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20210903142837.216978-1-janusz.krzysztofik@linux.intel.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions