From: Daniel Charles <daniel.charles@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>,
"Kamil Konieczny" <kamil.konieczny@linux.intel.com>,
igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t] tests/xe_compute_preempt: remove WMTP check in multiprocess tests
Date: Mon, 11 Aug 2025 14:22:26 -0700 [thread overview]
Message-ID: <f7786f2e-045b-4700-8ee3-77714244b2fb@intel.com> (raw)
In-Reply-To: <hq3btmoytyqwgvvux5snaozq7g3uux52uqygt7k5ew3276nxnd@lpy7kbiymexj>
On 8/11/2025 3:45 AM, Zbigniew Kempczyński wrote:
> On Mon, Aug 11, 2025 at 12:31:36PM +0200, Kamil Konieczny wrote:
>> Hi Zbigniew,
>> On 2025-08-11 at 07:46:51 +0200, Zbigniew Kempczyński wrote:
>>> Before forking we test WMTP preemption in test_compute_preempt()
>>> which is synchronous. Remove this check as it is redundant, there's
>>> dedicated 'compute-preempt' subtest which does it.
>> I do not see a dedicated VRAM test, only SYSTEM_RAM?
>> Something like: compute-preempt-vram?
> Generally on the beginning we just need to check if WMTP preemption
> is supported, memory doesn't matter. Tests which -vram are testing
> this functionality more thoroughly so adding compute-preempt-vram
> is not increasing our coverage.
Technically the tests changed from *-many to *-twice, nit-pick but it
can avoid confusions later
in any case, it looks good to me
--
Daniel.
>> I do not think it is a blocker so
>> Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> Thanks for the review.
>
> --
> Zbigniew
>
>>> Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
>>> Cc: Daniel Charles <daniel.charles@intel.com>
>>> ---
>>> tests/intel/xe_compute_preempt.c | 4 ----
>>> 1 file changed, 4 deletions(-)
>>>
>>> diff --git a/tests/intel/xe_compute_preempt.c b/tests/intel/xe_compute_preempt.c
>>> index 7a468e7426..c9b194869c 100644
>>> --- a/tests/intel/xe_compute_preempt.c
>>> +++ b/tests/intel/xe_compute_preempt.c
>>> @@ -102,7 +102,6 @@ igt_main
>>> igt_debug("RAM: %" PRIu64 ", child count: %d\n",
>>> ram_mb, child_count);
>>>
>>> - test_compute_preempt(xe, hwe, false, EXECENV_PREF_SYSTEM);
>>> igt_fork(child, child_count)
>>> test_compute_preempt(xe, hwe, false, EXECENV_PREF_SYSTEM);
>>> igt_waitchildren();
>>> @@ -129,7 +128,6 @@ igt_main
>>> igt_debug("RAM: %" PRIu64 ", child count: %d\n",
>>> ram_mb, child_count);
>>>
>>> - test_compute_preempt(xe, hwe, false, EXECENV_PREF_SYSTEM);
>>> igt_fork(child, child_count)
>>> test_compute_preempt(xe, hwe, false, EXECENV_PREF_SYSTEM);
>>> igt_waitchildren();
>>> @@ -156,7 +154,6 @@ igt_main
>>> igt_debug("VRAM: %" PRIu64 ", child count: %d\n",
>>> vram_mb, child_count);
>>>
>>> - test_compute_preempt(xe, hwe, false, EXECENV_PREF_VRAM);
>>> igt_fork(child, child_count)
>>> test_compute_preempt(xe, hwe, false, EXECENV_PREF_VRAM);
>>> igt_waitchildren();
>>> @@ -183,7 +180,6 @@ igt_main
>>> igt_debug("VRAM: %" PRIu64 ", child count: %d\n",
>>> vram_mb, child_count);
>>>
>>> - test_compute_preempt(xe, hwe, false, EXECENV_PREF_VRAM);
>>> igt_fork(child, child_count)
>>> test_compute_preempt(xe, hwe, false, EXECENV_PREF_VRAM);
>>> igt_waitchildren();
>>> --
>>> 2.43.0
>>>
prev parent reply other threads:[~2025-08-11 21:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 5:46 [PATCH i-g-t] tests/xe_compute_preempt: remove WMTP check in multiprocess tests Zbigniew Kempczyński
2025-08-11 6:26 ` ✓ i915.CI.BAT: success for " Patchwork
2025-08-11 6:43 ` ✓ Xe.CI.BAT: " Patchwork
2025-08-11 7:48 ` ✗ Xe.CI.Full: failure " Patchwork
2025-08-11 10:42 ` Zbigniew Kempczyński
2025-08-11 8:04 ` ✗ i915.CI.Full: " Patchwork
2025-08-11 10:43 ` Zbigniew Kempczyński
2025-08-11 10:31 ` [PATCH i-g-t] " Kamil Konieczny
2025-08-11 10:45 ` Zbigniew Kempczyński
2025-08-11 21:22 ` Daniel Charles [this message]
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=f7786f2e-045b-4700-8ee3-77714244b2fb@intel.com \
--to=daniel.charles@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.