diff options
| author | Chris Wilson <chris@chris-wilson.co.uk> | 2019-02-13 22:48:05 +0000 |
|---|---|---|
| committer | Chris Wilson <chris@chris-wilson.co.uk> | 2019-02-15 09:37:31 +0000 |
| commit | c836eb79c033c2be13aa8b41729b28d2ab1f72ab (patch) | |
| tree | 0c07cb93e84703e8372c1364e4f9b425b39b2fd3 /drivers/gpu/drm/i915/i915_request.c | |
| parent | 9a3b19a16dc28ab717cf1663d09ffee0715b735a (diff) | |
| download | kernel_replicant_linux-c836eb79c033c2be13aa8b41729b28d2ab1f72ab.tar.gz kernel_replicant_linux-c836eb79c033c2be13aa8b41729b28d2ab1f72ab.tar.bz2 kernel_replicant_linux-c836eb79c033c2be13aa8b41729b28d2ab1f72ab.zip | |
drm/i915/selftests: Always use an active engine while resetting
Currently, we only try to reset a live engine for checking the whitelist
retention across a per-engine reset. For safety, it appears we need to
prime the system with a hanging spinner before performing a full-device
reset. (Figuring out the root cause behind the instability with handling
a reset during a no-op request is a challenge for another test, the
whitelist test has its own purpose.)
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109626
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Link: https://patchwork.freedesktop.org/patch/msgid/20190213224805.32021-1-chris@chris-wilson.co.uk
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Diffstat (limited to 'drivers/gpu/drm/i915/i915_request.c')
0 files changed, 0 insertions, 0 deletions