igt/gem_exec_nop: Restore SLOW_QUICK loop terminator

The upper bound for SLOW_QUICK was added for the benefit of the slow
simulator, not because, as I wrongly thought, of the latency
measurements.

SLOW_QUICK was added in

commit d1e862324b747a0ab5d985eaa6830076817231c5
Author: Damien Lespiau <damien.lespiau@intel.com>
Date:   Mon Mar 25 20:06:20 2013 +0000

    tests: Instrument tests run in simulation to run quickly

and dropped in

commit 89bcdb9022fb7a1f66635b9f2546356ad0c0761a
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Tue Dec 8 13:42:50 2015 +0000

    igt/gem_exec_nop: Remove nop latency measurements

Reported-by: Ben Widawsky <benjamin.widawsky@intel.com>
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
This commit is contained in:
Chris Wilson 2015-12-16 19:51:08 +00:00
parent a012e44b6a
commit 04bd964527

View File

@ -71,7 +71,7 @@ static void loop(int fd, uint32_t handle, unsigned ring_id, const char *ring_nam
}
gem_sync(fd, handle);
for (count = 1; count <= 1<<17; count <<= 1) {
for (count = 1; count <= SLOW_QUICK(1<<17, 1<<4); count <<= 1) {
int loops = count;
gem_set_domain(fd, handle, I915_GEM_DOMAIN_GTT, 0);
while (loops--)