From: "Sharma, Nishit" <nishit.sharma@intel.com>
To: Varun Gupta <varun.gupta@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: <priyanka.dandamudi@intel.com>, <thomas.hellstrom@intel.com>
Subject: Re: [PATCH i-g-t] tests/intel/xe_evict: Drop blanket skip when system memory < VRAM
Date: Wed, 30 Sep 2026 09:19:00 +0530 [thread overview]
Message-ID: <94ab51b5-d08a-46cc-807a-5a9f1cf281e4@intel.com> (raw)
In-Reply-To: <20260929173928.3098760-2-varun.gupta@intel.com>
Hi Varun
On 9/29/2026 11:09 PM, Varun Gupta wrote:
> Since working_set() already clamps each subtest's allocation to what
> fits in VRAM plus 4/5 of available system memory, and every subtest
> loop has its own igt_skip_on_f(!ws) for cases that end up too small
> to run. The fixture-level skip is therefore redundant and skips the
> entire eviction suite.
> Remove the skip and rely on the per-subtest working_set() sizing.
>
> Signed-off-by: Varun Gupta <varun.gupta@intel.com>
> ---
> tests/intel/xe_evict.c | 9 ---------
> 1 file changed, 9 deletions(-)
>
> diff --git a/tests/intel/xe_evict.c b/tests/intel/xe_evict.c
> index 5a7298db0..230357419 100644
> --- a/tests/intel/xe_evict.c
> +++ b/tests/intel/xe_evict.c
> @@ -911,15 +911,6 @@ int igt_main()
> igt_assert(vram_size);
> system_size = igt_get_avail_ram_mb() << 20;
>
> - /* Test requires SRAM to about as big as VRAM. For example, small-cm creates
> - * (448 / 2) BOs with a size (1 / 128) of the total VRAM size. For
> - * simplicity ensure the SRAM size >= VRAM before running this test.
> - */
> - igt_skip_on_f(system_size < vram_size,
> - "System memory %llu MiB is less than local memory %llu MiB\n",
> - (unsigned long long)system_size >> 20,
> - (unsigned long long)vram_size >> 20);
> -
Can we put some message here why skip was removed, Something like:
No System vs VRAM size check needed as working_set() below limits each
subtest to what fits in VRAM/SRAM
and a subtest skips on its own when nothing fits i.e. igt_skip(!ws, ...)
> xe_for_each_engine(fd, hwe)
> if (hwe->engine_class != DRM_XE_ENGINE_CLASS_COPY)
> break;
Rest LGTM:
Reviewed-by: Nishit Sharma <nishit.sharma@intel.com>
next prev parent reply other threads:[~2026-09-30 3:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 17:39 [PATCH i-g-t] tests/intel/xe_evict: Drop blanket skip when system memory < VRAM Varun Gupta
2026-09-29 22:42 ` ✓ i915.CI.BAT: success for " Patchwork
2026-09-29 23:42 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-09-30 3:49 ` Sharma, Nishit [this message]
2026-09-30 9:53 ` [PATCH i-g-t] " Gupta, Varun
2026-09-30 5:37 ` ✗ Xe.CI.FULL: failure for " Patchwork
2026-09-30 10:04 ` Gupta, Varun
2026-09-30 9:52 ` ✓ i915.CI.Full: success " Patchwork
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=94ab51b5-d08a-46cc-807a-5a9f1cf281e4@intel.com \
--to=nishit.sharma@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=priyanka.dandamudi@intel.com \
--cc=thomas.hellstrom@intel.com \
--cc=varun.gupta@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