[PATCH] tests/xe_exec_threads: relax data check in multi-queue hang mode

[Xin Wang <x.wang@intel.com>]

In multi-queue hang mode, a reset of any queue in a queue group will
cause the entire group to reset. And since GuC only submits on the
primary queue, without explicit barriers or priority differences
between queues, we can't guarantee which queue hardware will pick up
on submission. As such, we don't know which queues will complete
prior to the group reset and need to check for all possible values.

Suggested-by: Stuart Summers <stuart.summers@intel.com>
Signed-off-by: Xin Wang <x.wang@intel.com>
---
 tests/intel/xe_exec_threads.c | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/tests/intel/xe_exec_threads.c b/tests/intel/xe_exec_threads.c
index 40a6c0c6d..9331a3b88 100644
--- a/tests/intel/xe_exec_threads.c
+++ b/tests/intel/xe_exec_threads.c
@@ -707,10 +707,15 @@ test_legacy_mode(int fd, uint32_t vm, uint64_t addr, uint64_t userptr,
 	     i < n_execs; i++) {
 		int e = i % n_exec_queues;
 
-		if (flags & HANG && e == hang_exec_queue)
+		if (flags & HANG && e == hang_exec_queue) {
 			igt_assert_eq(data[i].data, 0x0);
-		else
-			igt_assert_eq(data[i].data, 0xc0ffee);
+		} else {
+			/* Multi-queue reset affects all queues; data outcome is non-deterministic */
+			if (flags & HANG && flags & MULTI_QUEUE)
+				igt_assert(data[i].data == 0x0 || data[i].data == 0xc0ffee);
+			else
+				igt_assert_eq(data[i].data, 0xc0ffee);
+		}
 	}
 
 	syncobj_destroy(fd, sync[0].handle);
-- 
2.43.0