From: Sobin Thomas <sobin.thomas@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: zbigniew.kempczynski@intel.com, kamil.konieczny@intel.com,
Sobin Thomas <sobin.thomas@intel.com>
Subject: [PATCH v3 i-g-t 0/1] tests/intel/xe_compute_preempt: Compute preemption check
Date: Wed, 10 Sep 2025 17:19:58 +0000 [thread overview]
Message-ID: <20250910171959.1852534-1-sobin.thomas@intel.com> (raw)
On platforms like PVC that lack walker mid-thread preemption, running
tests in forked threads can cause inconsistent states due to mid-
execution igt_skip calls. This patch adds a kernel preemption check
at the start of each subtest to ensure consistent behavior. If the
GPU lacks required preemption, the test is skipped gracefully.
v2: Moved compatibility check to igt_fixture per review.
v3: - Added thread group preemption and WMTP checks;
- Introduced enum flags for preemption types. [Zbigniew]
Signed-off-by: Sobin Thomas <sobin.thomas@intel.com>
Sobin Thomas (1):
tests/intel/xe_compute_preempt: Compute preemption check
lib/intel_compute.c | 22 ++++++++++++++++++++++
lib/intel_compute.h | 7 +++++++
tests/intel/xe_compute_preempt.c | 6 ++++++
3 files changed, 35 insertions(+)
--
2.34.1
next reply other threads:[~2025-09-10 17:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 17:19 Sobin Thomas [this message]
2025-09-10 17:19 ` [PATCH v3 i-g-t 1/1] tests/intel/xe_compute_preempt: Compute preemption check Sobin Thomas
2025-09-11 6:49 ` Dandamudi, Priyanka
2025-09-11 11:58 ` Thomas, Sobin
2025-09-11 7:16 ` Zbigniew Kempczyński
2025-09-10 18:08 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-09-10 18:09 ` ✓ i915.CI.BAT: " Patchwork
2025-09-11 0:57 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-11 15:05 ` ✓ 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=20250910171959.1852534-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.