From: Sobin Thomas <sobin.thomas@intel.com>
To: igt-dev@lists.freedesktop.org, kamil.konieczny@intel.com
Cc: zbigniew.kempczynski@intel.com, Sobin Thomas <sobin.thomas@intel.com>
Subject: [PATCH i-g-t 0/1] tests/intel/xe_compute_preempt: Compute preemption check
Date: Mon, 15 Sep 2025 05:31:06 +0000 [thread overview]
Message-ID: <20250915053107.10980-1-sobin.thomas@intel.com> (raw)
On platforms (like PVC) that do not support walker mid-thread
preemption, running tests in forked threads can lead to inconsistent
states due to igt_skip being called mid-execution. Made changes to
perform kernel preemption check at the beginning of each subtests.
If the GPU version does not support the required features, the
test is skipped gracefully, ensuring consistent behavior across
different platforms.
v2: Fixed review comments to move the compatibility check
into the igt_fixture.
v3: Added check for thread group preemption and WMTP.
Added enum flags for preemption type as per review . [Zbigniew]
v4: Added check for preempt inside __run_intel_compute_kernel_preempt.
Refactored the code into functions.
Sobin Thomas (1):
tests/intel/xe_compute_preempt: Compute preemption check
lib/intel_compute.c | 50 ++++++++++++++++++++++++++++----
lib/intel_compute.h | 7 +++++
tests/intel/xe_compute_preempt.c | 6 ++++
3 files changed, 57 insertions(+), 6 deletions(-)
--
2.34.1
next reply other threads:[~2025-09-15 5:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 5:31 Sobin Thomas [this message]
2025-09-15 5:31 ` [PATCH i-g-t 1/1] tests/intel/xe_compute_preempt: Compute preemption check Sobin Thomas
2025-09-15 8:09 ` Zbigniew Kempczyński
2025-09-15 6:33 ` ✓ Xe.CI.BAT: success for tests/intel/xe_compute_preempt: Compute preemption check (rev2) Patchwork
2025-09-15 6:39 ` ✓ i915.CI.BAT: " Patchwork
2025-09-15 8:13 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-15 8:44 ` ✓ 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=20250915053107.10980-1-sobin.thomas@intel.com \
--to=sobin.thomas@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@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.