[Intel-gfx] [PATCH i-g-t] tests/gem_exec_gttfill: Fix require memory assertion and tune down the timeout test for BAT.

[Marius Vlad]

There's no need to multiply the number of batches with the number of
engines as intel_require_memory() already compares against the aperture
size (count * BATCH_SIZE).
This also removes the weird assertion messages where we need
bogus amounts of RAM.

Also tune down the timeout from from 10s to 2s to speed up BAT.

CC: Chris Wilson <chris at chris-wilson.co.uk>
Signed-off-by: Marius Vlad <marius.c.vlad at intel.com>
---
 tests/gem_exec_gttfill.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tests/gem_exec_gttfill.c b/tests/gem_exec_gttfill.c
index 5921923..4778e4d 100644
--- a/tests/gem_exec_gttfill.c
+++ b/tests/gem_exec_gttfill.c
@@ -144,7 +144,7 @@ static void fillgtt(int fd, unsigned ring, int timeout)
 	count = size / BATCH_SIZE + 1;
 	igt_debug("Using %'d batches to fill %'llu aperture on %d engines\n",
 		  count, (long long)size, nengine);
-	intel_require_memory(count * nengine, BATCH_SIZE, CHECK_RAM);
+	intel_require_memory(count, BATCH_SIZE, CHECK_RAM);
 
 	memset(&execbuf, 0, sizeof(execbuf));
 	execbuf.buffer_count = 1;
@@ -195,7 +195,7 @@ igt_main
 	igt_fork_hang_detector(device);
 
 	igt_subtest("basic")
-		fillgtt(device, 0, 10);
+		fillgtt(device, 0, 2);
 
 	for (e = intel_execution_engines; e->name; e++)
 		igt_subtest_f("%s", e->name)
-- 
2.5.0