Before running a hang test, check if we can inject a hang and expect
recover to work. If we can't control a hang, skip the subtest.
Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
---
tests/kms_vblank.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/tests/kms_vblank.c b/tests/kms_vblank.c
index 2bee49de5..508c0fa03 100644
--- a/tests/kms_vblank.c
+++ b/tests/kms_vblank.c
@@ -442,10 +442,14 @@ static void run_subtests_for_pipe(data_t *data)
igt_subtest_f("pipe-%s-%s-%s-hang",
kmstest_pipe_name(data->pipe),
f->name, m->name) {
+ igt_hang_t hang;
+
+ hang = igt_allow_hang(data->display.drm_fd, 0, 0);
for_each_valid_output_on_pipe(&data->display, data->pipe, data->output) {
data->flags = m->flags;
run_test(data, f->func);
}
+ igt_disallow_hang(data->display.drm_fd, hang);
}
}
}
--
2.18.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
