On 25/03/2022 10:18, Petri Latvala wrote:
On Thu, Mar 24, 2022 at 02:26:20PM +0000, Matthew Auld wrote:
From: CQ Tang <cq.t...@intel.com>
On some systems lmem can be as large as 16G, which seems to trigger
various CI timeouts, and in the best case just takes a long time. For
the purposes of the test we should be able to limit to 4G, without any
big loss in coverage.
Signed-off-by: CQ Tang <cq.t...@intel.com>
Signed-off-by: Matthew Auld <matthew.a...@intel.com>
Cc: Thomas Hellström <thomas.hellst...@linux.intel.com>
Cc: Nirmoy Das <nirmoy....@linux.intel.com>
---
tests/i915/gem_lmem_swapping.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/tests/i915/gem_lmem_swapping.c b/tests/i915/gem_lmem_swapping.c
index 995a663f..ad1c989c 100644
--- a/tests/i915/gem_lmem_swapping.c
+++ b/tests/i915/gem_lmem_swapping.c
@@ -526,7 +526,13 @@ igt_main_args("", long_options, help_str, opt_handler,
NULL)
igt_fixture {
struct intel_execution_engine2 *e;
- i915 = drm_open_driver(DRIVER_INTEL);
+ igt_i915_driver_unload();
+ if (igt_i915_driver_load("lmem_size=4096")) {
+ igt_debug("i915 missing lmem_size modparam support\n");
+ igt_assert_eq(igt_i915_driver_load(NULL), 0);
+ }
Does the driver load truly fail with an unknown param?
Yeah, I have since removed that. From the CI logs it just loads anyway...
