With the vebox 2 patches the number of internal rings don't match the
number of exposed rings. So add another subtest with an invalid ring
which should be invalid both internally and externally. The bug this
will catch is using the ring structure before validation, which the
old "invalide-ring" wont be able to due to the internal vebox2 ring.
Signed-off-by: Daniel Vetter <daniel.vetter@xxxxxxxx>
---
tests/gem_exec_params.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/tests/gem_exec_params.c b/tests/gem_exec_params.c
index 306039c244e3..769969d3fe56 100644
--- a/tests/gem_exec_params.c
+++ b/tests/gem_exec_params.c
@@ -117,6 +117,11 @@ igt_main
RUN_FAIL(EINVAL);
}
igt_subtest("invalid-ring") {
+ execbuf.flags = I915_EXEC_RING_MASK;
+ RUN_FAIL(EINVAL);
+ }
+
+ igt_subtest("invalid-ring2") {
execbuf.flags = LOCAL_I915_EXEC_VEBOX+1;
RUN_FAIL(EINVAL);
}
--
1.8.1.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
