diff options
author | 2018-12-13 09:15:20 +0000 | |
---|---|---|
committer | 2018-12-13 10:07:54 +0000 | |
commit | 921f3a60e54e751ce1393deef6218c5900558b3d (patch) | |
tree | b8068f28490f817b553138299741c17c2ff26291 /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | drm/i915/selftests: Check we can recover a wedged device (diff) | |
download | wireguard-linux-921f3a60e54e751ce1393deef6218c5900558b3d.tar.xz wireguard-linux-921f3a60e54e751ce1393deef6218c5900558b3d.zip |
drm/i915/selftests: Verify we can perform resets from atomic context
We currently require that our per-engine reset can be called from any
context, even hardirq, and in the future wish to perform the device
reset without holding struct_mutex (which requires some lockless
shenanigans that demand the lowlevel intel_reset_gpu() be able to be
used in atomic context). Test that we meet the current requirements by
calling i915_reset_engine() from under various atomic contexts.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20181213091522.2926-2-chris@chris-wilson.co.uk
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions