From: Stuart Summers <stuart.summers@intel.com>
Cc: igt-dev@lists.freedesktop.org,
niranjana.vishwanathapura@intel.com,
Stuart Summers <stuart.summers@intel.com>,
Priyanka Dandamudi <priyanka.dandamudi@intel.com>
Subject: [PATCH i-g-t 1/4] tests/intel/xe_exec_reset: Remove CANCEL logic for CM variants
Date: Mon, 27 Apr 2026 21:20:30 +0000 [thread overview]
Message-ID: <20260427212034.18486-2-stuart.summers@intel.com> (raw)
In-Reply-To: <20260427212034.18486-1-stuart.summers@intel.com>
The compute mode tests are expected to be long running and will
not trigger the TDR logic in the KMD. This is illustrated in
the test in that the legacy cases implement the CANCEL case,
which is meant to trigger the TDR based resets vs the CM
cases which do not support this.
Remove the CANCEL logic from the CM tests since it isn't actually
used in any of the test cases here.
Signed-off-by: Stuart Summers <stuart.summers@intel.com>
Acked-by: Priyanka Dandamudi <priyanka.dandamudi@intel.com>
Reviewed-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
---
tests/intel/xe_exec_reset.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/intel/xe_exec_reset.c b/tests/intel/xe_exec_reset.c
index 66580ea44..bc1a74fa3 100644
--- a/tests/intel/xe_exec_reset.c
+++ b/tests/intel/xe_exec_reset.c
@@ -422,7 +422,7 @@ test_compute_mode(int fd, struct drm_xe_engine_class_instance *eci,
uint64_t exec_addr;
int e = i % n_exec_queues;
- if (!i || flags & CANCEL) {
+ if (!i) {
spin_opts.addr = base_addr + spin_offset;
xe_spin_init(&data[i].spin, &spin_opts);
exec_addr = spin_opts.addr;
@@ -479,7 +479,7 @@ test_compute_mode(int fd, struct drm_xe_engine_class_instance *eci,
xe_vm_unbind_async(fd, vm, 0, 0, addr, bo_size, sync, 1);
xe_wait_ufence(fd, &data[0].vm_sync, USER_FENCE_VALUE, 0, 3 * NSEC_PER_SEC);
- if (!(flags & (GT_RESET | CANCEL))) {
+ if (!(flags & GT_RESET)) {
for (i = 1; i < n_execs; i++)
igt_assert_eq(data[i].data, 0xc0ffee);
}
--
2.43.0
next prev parent reply other threads:[~2026-04-27 21:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 21:20 [PATCH i-g-t 0/4] Add test coverage for multi queue reset Stuart Summers
2026-04-27 21:20 ` Stuart Summers [this message]
2026-04-27 21:20 ` [PATCH i-g-t 2/4] tests/intel/xe_exec_reset: Add a comment about return for syncobj wait Stuart Summers
2026-04-27 21:20 ` [PATCH i-g-t 3/4] tests/intel/xe_exec_reset: Add checks for hanging queue wait_ufence return Stuart Summers
2026-04-27 21:20 ` [PATCH i-g-t 4/4] tests/intel/xe_exec_reset: Add multi queue subtests Stuart Summers
2026-04-28 1:52 ` ✓ i915.CI.BAT: success for Add test coverage for multi queue reset (rev2) Patchwork
2026-04-28 2:26 ` ✗ Xe.CI.BAT: failure " 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=20260427212034.18486-2-stuart.summers@intel.com \
--to=stuart.summers@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=niranjana.vishwanathapura@intel.com \
--cc=priyanka.dandamudi@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