From: Matthew Auld <matthew.auld@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-gfx@lists.freedesktop.org,
"Nirmoy Das" <nirmoy.das@intel.com>,
"CQ Tang" <cq.tang@intel.com>
Subject: [Intel-gfx] [PATCH i-g-t v2] tests/gem_lmem_swapping: limit lmem to 4G
Date: Mon, 28 Mar 2022 10:29:59 +0100 [thread overview]
Message-ID: <20220328092959.790392-1-matthew.auld@intel.com> (raw)
From: CQ Tang <cq.tang@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.
v2:
- No need to try again without the modparam; if it's not supported it
will still load the driver just fine.
Signed-off-by: CQ Tang <cq.tang@intel.com>
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Cc: Nirmoy Das <nirmoy.das@linux.intel.com>
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
---
tests/i915/gem_lmem_swapping.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/tests/i915/gem_lmem_swapping.c b/tests/i915/gem_lmem_swapping.c
index 31644bcd..69f7bae9 100644
--- a/tests/i915/gem_lmem_swapping.c
+++ b/tests/i915/gem_lmem_swapping.c
@@ -527,7 +527,10 @@ 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();
+ igt_assert_eq(igt_i915_driver_load("lmem_size=4096"), 0);
+
+ i915 = __drm_open_driver(DRIVER_INTEL);
igt_require_gem(i915);
igt_require(gem_has_lmem(i915));
@@ -556,6 +559,7 @@ igt_main_args("", long_options, help_str, opt_handler, NULL)
intel_ctx_destroy(i915, ctx);
free(regions);
close(i915);
+ igt_i915_driver_unload();
}
igt_exit();
--
2.34.1
next reply other threads:[~2022-03-28 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 9:29 Matthew Auld [this message]
2022-03-28 9:40 ` [Intel-gfx] [igt-dev] [PATCH i-g-t v2] tests/gem_lmem_swapping: limit lmem to 4G Petri Latvala
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220328092959.790392-1-matthew.auld@intel.com \
--to=matthew.auld@intel.com \
--cc=cq.tang@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nirmoy.das@intel.com \
--cc=thomas.hellstrom@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox