Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: nishit.sharma@intel.com
To: igt-dev@lists.freedesktop.org, kamil.konieczny@intel.com
Subject: [PATCH v2 2/9] tests/intel/xe_exec_reset: add sync concurrent reset submit subtest
Date: Tue, 18 Aug 2026 04:08:38 +0000	[thread overview]
Message-ID: <20260818040845.548727-3-nishit.sharma@intel.com> (raw)
In-Reply-To: <20260818040845.548727-1-nishit.sharma@intel.com>

From: Nishit Sharma <nishit.sharma@intel.com>

Add gt-reset-concurrent-submit-sync to xe_exec_reset to stress concurrent
job submission while issuing synchronous GT resets.

Signed-off-by: Nishit Sharma <nishit.sharma@intel.com>
---
 tests/intel/xe_exec_reset.c | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/tests/intel/xe_exec_reset.c b/tests/intel/xe_exec_reset.c
index 134378974..407775cfc 100644
--- a/tests/intel/xe_exec_reset.c
+++ b/tests/intel/xe_exec_reset.c
@@ -132,6 +132,7 @@ static void test_spin(int fd, struct drm_xe_engine_class_instance *eci,
 #define COMPRESSION			(0x1 << 13)
 #define MULTI_QUEUE			(0x1 << 14)
 #define SECONDARY_QUEUE			(0x1 << 15)
+#define RESET_SYNC_MODE			(0x1 << 16)
 
 /**
  * SUBTEST: %s-cat-error
@@ -661,7 +662,10 @@ static void do_resets(struct gt_thread_data *t)
 	while (!*(t->exit)) {
 		usleep(250000);	/* 250 ms */
 		(*t->num_reset)++;
-		xe_force_gt_reset_async(t->fd, t->gt);
+		if (t->flags & RESET_SYNC_MODE)
+			xe_force_gt_reset_sync(t->fd, t->gt);
+		else
+			xe_force_gt_reset_async(t->fd, t->gt);
 	}
 }
 
@@ -736,6 +740,10 @@ static void *gt_reset_thread(void *data)
  * Description: Stress concurrent GT resets and job submissions
  * Test category: stress test
  *
+ * SUBTEST: gt-stress-reset-concurrent-submit-sync
+ * Description: Stress concurrent GT resets and job submissions with sync resets
+ * Test category: stress test
+ *
  */
 static void
 gt_reset(int fd, int gt, int n_threads, int n_sec, unsigned int flags)
@@ -953,6 +961,7 @@ int igt_main()
 	};
 	const struct section ssections[] = {
 		{ "reset-concurrent-submit", 0 },
+		{ "reset-concurrent-submit-sync", RESET_SYNC_MODE },
 		{ NULL },
 	};
 	int gt;
@@ -1151,7 +1160,7 @@ int igt_main()
 
 	for (const struct section *s = ssections; s->name; s++) {
 		igt_subtest_f("gt-stress-%s", s->name)
-			gt_reset(fd, 0, 8, 2, 0);
+			gt_reset(fd, 0, 8, 2, s->flags);
 	}
 
 	igt_subtest("gt-mocs-reset")
-- 
2.43.0


  parent reply	other threads:[~2026-08-18  4:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18  4:08 [PATCH v2 0/9] extend GT reset stress coverage nishit.sharma
2026-08-18  4:08 ` [PATCH v2 1/9] tests/intel/xe_exec_reset: Add concurrent GT reset submit stress test nishit.sharma
2026-08-18  4:08 ` nishit.sharma [this message]
2026-08-18  4:08 ` [PATCH v2 3/9] tests/intel/xe_exec_reset: add gt-stress-reset-memory-pressure subtest nishit.sharma
2026-08-18  4:08 ` [PATCH v2 4/9] tests/intel/xe_exec_reset: add gt-stress-reset-bo-invalidation subtest nishit.sharma
2026-08-18  4:08 ` [PATCH v2 5/9] tests/intel/xe_exec_reset: add gt-stress-reset-rapid-cycle subtest nishit.sharma
2026-08-18  4:08 ` [PATCH v2 6/9] tests/intel/xe_exec_reset: add gt-stress-reset-destroy-vm-context subtest nishit.sharma
2026-08-18  4:08 ` [PATCH v2 7/9] tests/intel/xe_exec_reset: add gt-stress-reset-mixed-engine-usage subtest nishit.sharma
2026-08-18  4:08 ` [PATCH v2 8/9] tests/intel/xe_exec_reset: add gt-stress-reset-pm-transition subtest nishit.sharma
2026-08-18  4:08 ` [PATCH v2 9/9] tests/intel/xe_exec_reset: add gt-stress-reset-engine-hang subtest nishit.sharma
2026-08-18  4:50 ` ✓ Xe.CI.BAT: success for extend GT reset stress coverage (rev2) Patchwork
2026-08-18  5:04 ` ✓ i915.CI.BAT: " Patchwork
2026-08-18  5:56 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-08-18 16:04 ` ✗ i915.CI.Full: " 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=20260818040845.548727-3-nishit.sharma@intel.com \
    --to=nishit.sharma@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@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