From: Sobin Thomas <sobin.thomas@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: zbigniew.kempczynski@intel.com, Sobin Thomas <sobin.thomas@intel.com>
Subject: [PATCH i-g-t 1/1] tests/xe_evict_ccs:Add check to update object param as per visible RAM
Date: Wed, 23 Jul 2025 15:05:08 +0000 [thread overview]
Message-ID: <20250723150508.552862-2-sobin.thomas@intel.com> (raw)
In-Reply-To: <20250723150508.552862-1-sobin.thomas@intel.com>
This change will modify the parameters for the test based on the
available visible ram and update the max object size that is calculated
based on the existing method
Signed-off-by: Sobin Thomas <sobin.thomas@intel.com>
---
tests/intel/xe_evict_ccs.c | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/tests/intel/xe_evict_ccs.c b/tests/intel/xe_evict_ccs.c
index 281d27015..9abff1389 100644
--- a/tests/intel/xe_evict_ccs.c
+++ b/tests/intel/xe_evict_ccs.c
@@ -343,6 +343,31 @@ static void set_config(int fd, uint32_t flags, const struct param *param,
igt_debug("nproc: %d, mem per proc: %dMB\n", nproc, config->mb_per_proc);
}
+static void adjust_params_for_vram_size(uint64_t vram_size)
+{
+ uint64_t vram_mb = vram_size / (1024 * 1024);
+ int recommended_max_size_kb;
+ bool user_set_max_size = (params.max_size_kb != MAX_OBJ_KB);
+ int max_object_mb = vram_mb / 64;
+
+ max_object_mb = max_t(int, 2, min_t(int, max_object_mb, 256));
+ recommended_max_size_kb = max_object_mb * 1024;
+
+ igt_info("VRAM (%"PRIu64"MB): Calculated %d%% usage, %dMB max objects\n",
+ vram_mb, params.vram_percent, max_object_mb);
+
+ if (user_set_max_size) {
+ igt_warn("User specified max object size (%dKB) may not be
+ optimal for %"PRIu64"MB VRAM (recommended: %dKB)\n",
+ params.max_size_kb, vram_mb, recommended_max_size_kb);
+ } else {
+ params.max_size_kb = recommended_max_size_kb;
+ }
+
+ igt_info("Final settings: %d%% VRAM, %dMB max object\n",
+ params.vram_percent, params.max_size_kb / 1024);
+}
+
static void evict_ccs(int fd, uint32_t flags, const struct param *param)
{
struct config config;
@@ -500,6 +525,7 @@ igt_main_args("bdDn:p:s:S:V", NULL, help_str, opt_handler, NULL)
igt_require(xe_has_vram(fd));
vram_size = xe_visible_vram_size(fd, 0);
igt_assert(vram_size);
+ adjust_params_for_vram_size(vram_size);
has_flatccs = HAS_FLATCCS(intel_get_drm_devid(fd));
}
--
2.34.1
next prev parent reply other threads:[~2025-07-23 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 15:05 [PATCH i-g-t 0/1] tests/xe_evict_ccs:Add check to update object param Sobin Thomas
2025-07-23 15:05 ` Sobin Thomas [this message]
2025-07-28 12:27 ` [PATCH i-g-t 1/1] tests/xe_evict_ccs:Add check to update object param as per visible RAM Kamil Konieczny
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=20250723150508.552862-2-sobin.thomas@intel.com \
--to=sobin.thomas@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=zbigniew.kempczynski@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