From 37b06eb9b526df6c23ec75f7a9ecd9547fa76695 Mon Sep 17 00:00:00 2001 From: Daniel Vetter Date: Thu, 3 Aug 2017 19:27:32 +0200 Subject: tests/kms_busy: Only test against one engine Back when we used cs flips it made sense to go through different engines, since a buffer busy on an engine that we couldnt' use for cs flipping ended up in different paths. But with atomic we use a worker for all flips, and going through the combinatorial growth of engines just wastes precious machine time. More so the more modern the platform is. Of course gem tests should still do some diagonal testing across all engines, but the kms side can afford to be a bit cheaper. v2: Make it compile. Oops. Also make sure we don't break fast-feedback.testlist. Adding a mode where we depend upon all engines isn't really possible, because there's only 1 exclusive fence and that's the only thing a flip waits for. Cc: Chris Wilson Cc: Maarten Lankhorst Cc: Arkadiusz Hiler Acked-by: Maarten Lankhorst Reviewed-by: Arkadiusz Hiler Signed-off-by: Daniel Vetter --- tests/intel-ci/fast-feedback.testlist | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'tests/intel-ci') diff --git a/tests/intel-ci/fast-feedback.testlist b/tests/intel-ci/fast-feedback.testlist index 02a222f2..79160624 100644 --- a/tests/intel-ci/fast-feedback.testlist +++ b/tests/intel-ci/fast-feedback.testlist @@ -196,9 +196,9 @@ igt@kms_addfb_basic@unused-handle igt@kms_addfb_basic@unused-modifier igt@kms_addfb_basic@unused-offsets igt@kms_addfb_basic@unused-pitches -igt@kms_busy@basic-flip-default-a -igt@kms_busy@basic-flip-default-b -igt@kms_busy@basic-flip-default-c +igt@kms_busy@basic-flip-a +igt@kms_busy@basic-flip-b +igt@kms_busy@basic-flip-c igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy igt@kms_cursor_legacy@basic-flip-after-cursor-atomic -- cgit v1.2.3