From: Petri Latvala <petri.latvala@intel.com>
To: Matthew Auld <matthew.auld@intel.com>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-gfx@lists.freedesktop.org, igt-dev@lists.freedesktop.org,
"CQ Tang" <cq.tang@intel.com>,
"Nirmoy Das" <nirmoy.das@intel.com>
Subject: Re: [Intel-gfx] [PATCH i-g-t v3] tests/gem_lmem_swapping: limit lmem to 4G
Date: Mon, 28 Mar 2022 14:18:09 +0300 [thread overview]
Message-ID: <YkGZcTZHHcF781Zz@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20220328100859.13550-1-matthew.auld@intel.com>
On Mon, Mar 28, 2022 at 11:08:59AM +0100, Matthew Auld wrote:
> 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.
> v3(Petri):
> - Add a helpful debug print in case the kernel is missing support for
> the lmem_size modparam.
>
> 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>
> Cc: Petri Latvala <petri.latvala@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 | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/tests/i915/gem_lmem_swapping.c b/tests/i915/gem_lmem_swapping.c
> index 31644bcd..6cf1acec 100644
> --- a/tests/i915/gem_lmem_swapping.c
> +++ b/tests/i915/gem_lmem_swapping.c
> @@ -526,11 +526,20 @@ igt_main_args("", long_options, help_str, opt_handler, NULL)
>
> igt_fixture {
> struct intel_execution_engine2 *e;
> + char *tmp;
>
> - 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));
>
> + tmp = __igt_params_get(i915, "lmem_size");
> + if (!tmp)
> + igt_info("lmem_size modparam not supported on this kernel. Continuing with full lmem size. This may result in CI timeouts.");
> + free(tmp);
Newline at the end missing. With that added,
Reviewed-by: Petri Latvala <petri.latvala@intel.com>
> +
> regions = gem_get_query_memory_regions(i915);
> igt_require(regions);
>
> @@ -556,6 +565,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 prev parent reply other threads:[~2022-03-28 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 10:08 [Intel-gfx] [PATCH i-g-t v3] tests/gem_lmem_swapping: limit lmem to 4G Matthew Auld
2022-03-28 11:18 ` Petri Latvala [this message]
2022-04-08 8:56 ` [Intel-gfx] [igt-dev] " Tvrtko Ursulin
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=YkGZcTZHHcF781Zz@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=cq.tang@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--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