diff options
author | Chris Wilson <chris@chris-wilson.co.uk> | 2018-01-03 18:09:07 +0000 |
---|---|---|
committer | Arkadiusz Hiler <arkadiusz.hiler@intel.com> | 2018-01-04 13:40:04 +0200 |
commit | 253f8c09f9bb986938c3e7590438228996bd150b (patch) | |
tree | d0b74d215c86d3b8a309293b4df3ebc421cb4ce1 | |
parent | 10ad981c6f912dc8cd10035fb50d939956b45b1c (diff) |
igt/perf_pmu: Skip GEM checks for repeated spin_batch allocations
Each call to igt_spin_batch_new_fence will do a stalling check to verify
that GEM is functional before submitting the spinning batch. In a loop,
this means that we may end up waiting for our earlier spinning
batches...
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-rw-r--r-- | tests/perf_pmu.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/tests/perf_pmu.c b/tests/perf_pmu.c index 85ce1739..45e2f614 100644 --- a/tests/perf_pmu.c +++ b/tests/perf_pmu.c @@ -833,7 +833,8 @@ test_interrupts(int gem_fd) /* Queue spinning batches. */ for (int i = 0; i < target; i++) { - spin[i] = igt_spin_batch_new_fence(gem_fd, 0, I915_EXEC_RENDER); + spin[i] = __igt_spin_batch_new_fence(gem_fd, + 0, I915_EXEC_RENDER); if (i == 0) { fence_fd = spin[i]->out_fence; } else { |