From d5657417d6e5ac67c5af17688246977de258bfaa Mon Sep 17 00:00:00 2001 From: Chris Wilson Date: Tue, 27 Mar 2018 09:33:09 +0100 Subject: igt/perf_pmu: Most-busy requires at least one busy engine The test is whether with all but one engine busy we record the correct load on each engine. If we only have one engine, this test degenerates into all-idle/all-busy, so we can skip to avoid crashing on the assumption that we have a busy spinner. Signed-off-by: Chris Wilson Cc: Tvrtko Ursulin Reviewed-by: Tvrtko Ursulin --- tests/perf_pmu.c | 1 + 1 file changed, 1 insertion(+) (limited to 'tests/perf_pmu.c') diff --git a/tests/perf_pmu.c b/tests/perf_pmu.c index f27b7ec7..b59af818 100644 --- a/tests/perf_pmu.c +++ b/tests/perf_pmu.c @@ -513,6 +513,7 @@ most_busy_check_all(int gem_fd, const struct intel_execution_engine2 *e, val[i++] = I915_PMU_ENGINE_BUSY(e_->class, e_->instance); } igt_assert(i == num_engines); + igt_require(spin); /* at least one busy engine */ fd[0] = -1; for (i = 0; i < num_engines; i++) -- cgit v1.2.3