From 7c8f2616fa0fd3ddb16e050c5b7ea9ce707abbe4 Mon Sep 17 00:00:00 2001 From: Chris Wilson Date: Tue, 26 Mar 2019 18:54:19 +0000 Subject: i915/gem_exec_big: 128MiB not enough slack? Let out the rope! Even with 128MiB reserved for other use, a single pass of gem_exec_big runs out of memory. Give in and halve our batch size, that has to be enough slack! As to why it keeps on failing, is left as an exercise to the reader -- we have to solve the mm/ mystery one day, as eventually it will be our only remaining source of bugs! Signed-off-by: Chris Wilson Cc: Tvrtko Ursulin Reviewed-by: Tvrtko Ursulin --- tests/i915/gem_exec_big.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tests/i915') diff --git a/tests/i915/gem_exec_big.c b/tests/i915/gem_exec_big.c index 015f59e2..440136ee 100644 --- a/tests/i915/gem_exec_big.c +++ b/tests/i915/gem_exec_big.c @@ -260,7 +260,7 @@ static void single(int i915) uint32_t handle; void *ptr; - batch_size = (intel_get_avail_ram_mb() - 128) << 20; /* CI slack */ + batch_size = (intel_get_avail_ram_mb() / 2) << 20; /* XXX CI slack? */ limit = gem_aperture_size(i915) - (256 << 10); /* low pages reserved */ if (!gem_uses_full_ppgtt(i915)) limit = 3 * limit / 4; -- cgit v1.2.3