The pair of *-hang-all will generate sufficient hangs for the kernel to
ban the client. This is unfortunate as it means all further tests are
skipped. Ask nicely not to be banned.
Signed-off-by: Chris Wilson <ch...@chris-wilson.co.uk>
---
tests/i915/gem_exec_fence.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/tests/i915/gem_exec_fence.c b/tests/i915/gem_exec_fence.c
index d2d26a28b..4e8bdd7b3 100644
--- a/tests/i915/gem_exec_fence.c
+++ b/tests/i915/gem_exec_fence.c
@@ -1522,6 +1522,8 @@ igt_main
}
igt_subtest_group {
+ igt_hang_t hang;
+
igt_fixture {
igt_fork_hang_detector(i915);
}
@@ -1533,12 +1535,17 @@ igt_main
igt_fixture {
igt_stop_hang_detector();
+ hang = igt_allow_hang(i915, 0, 0);
}
igt_subtest("busy-hang-all")
test_fence_busy_all(i915, HANG);
igt_subtest("wait-hang-all")
test_fence_busy_all(i915, WAIT | HANG);
+
+ igt_fixture {
+ igt_disallow_hang(i915, hang);
+ }
}
for (e = intel_execution_engines; e->name; e++) {
--
2.24.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
