If the legacy ringbuffer doesn't support scheduling, it doesn't set the
cap! Hypothetically if one were to enable ringbuffer scheduling, this is
part of its testing suite.
Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
---
tests/i915/gem_exec_schedule.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/tests/i915/gem_exec_schedule.c b/tests/i915/gem_exec_schedule.c
index 7b4186228..4ccacba41 100644
--- a/tests/i915/gem_exec_schedule.c
+++ b/tests/i915/gem_exec_schedule.c
@@ -1774,9 +1774,6 @@ igt_main
igt_fixture {
igt_require(gem_scheduler_enabled(fd));
igt_require(gem_scheduler_has_ctx_priority(fd));
-
- /* need separate rings */
- igt_require(gem_has_execlists(fd));
}
for (e = intel_execution_engines; e->name; e++) {
--
2.22.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
