All of lore.kernel.org
 help / color / mirror / Atom feed
From: fei.yang@intel.com
To: igt-dev@lists.freedesktop.org
Cc: Fei Yang <fei.yang@intel.com>
Subject: [i-g-t, v2, 3/4] tests/intel/xe_exec_threads: wait for all submissions to complete
Date: Thu,  7 Nov 2024 17:10:40 -0800	[thread overview]
Message-ID: <20241108011041.2257553-4-fei.yang@intel.com> (raw)
In-Reply-To: <20241108011041.2257553-1-fei.yang@intel.com>

From: Fei Yang <fei.yang@intel.com>

In test_compute_mode, there is an one second sleep waiting for all the
submissions to complete, but a hardcode wait is not reliable for test
that could have thousands of xe_execs submissions. Instead we should
wait for the ufence to make sure the GPU is inactive before unbinding
the BO.

Signed-off-by: Fei Yang <fei.yang@intel.com>
---
 tests/intel/xe_exec_threads.c | 28 ++++++++++++++++++++++------
 1 file changed, 22 insertions(+), 6 deletions(-)

diff --git a/tests/intel/xe_exec_threads.c b/tests/intel/xe_exec_threads.c
index 962957cd7..433f2620a 100644
--- a/tests/intel/xe_exec_threads.c
+++ b/tests/intel/xe_exec_threads.c
@@ -404,16 +404,32 @@ test_compute_mode(int fd, uint32_t vm, uint64_t addr, uint64_t userptr,
 		}
 	}
 
-	j = flags & INVALIDATE ?
-		(flags & RACE ? n_execs / 2 + 1 : n_execs - 1) : 0;
+	j = 0; /* wait for all submissions to complete */
+	if (flags & INVALIDATE)
+		/*
+		 * For !RACE cases xe_wait_ufence has been called in above for-loop
+		 * except the last batch of submissions. For RACE cases we will need
+		 * to wait for the second half of the submissions to complete. There
+		 * is a potential race here because the first half submissions might
+		 * have updated the fence in the old physical location while the test
+		 * is remapping the buffer from a different physical location, but the
+		 * wait_ufence only checks the fence from the new location which would
+		 * never be updated. We have to assume the first half of the submissions
+		 * complete before the second half. Will have a follow up patch to fix
+		 * this completely.
+		 */
+		j = (flags & RACE) ? (n_execs / 2 + 1) : (((n_execs - 1) & ~0x1f) + 1);
+	else if (flags & REBIND)
+		/*
+		 * For REBIND cases xe_wait_ufence has been called in above for-loop
+		 * except the last batch of submissions.
+		 */
+		j = ((n_execs - 1) & ~0x1f) + 1;
+
 	for (i = j; i < n_execs; i++)
 		xe_wait_ufence(fd, &data[i].exec_sync, USER_FENCE_VALUE,
 			       exec_queues[i % n_exec_queues], fence_timeout);
 
-	/* Wait for all execs to complete */
-	if (flags & INVALIDATE)
-		sleep(1);
-
 	sync[0].addr = to_user_pointer(&data[0].vm_sync);
 	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, fence_timeout);
-- 
2.25.1


  parent reply	other threads:[~2024-11-08  1:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08  1:10 [i-g-t, v2, 0/4] separate sync data and batch buffer fei.yang
2024-11-08  1:10 ` [i-g-t, v2, 1/4] tests/intel/xe_exec_fault_mode: separate exec_sync " fei.yang
2024-11-12 13:23   ` Nirmoy Das
2024-11-08  1:10 ` [i-g-t, v2, 2/4] tests/intel/xe_exec_threads: remove redundant wait fei.yang
2024-11-08  1:10 ` fei.yang [this message]
2024-11-12 13:14   ` [i-g-t, v2, 3/4] tests/intel/xe_exec_threads: wait for all submissions to complete Nirmoy Das
2024-11-08  1:10 ` [i-g-t, v2, 4/4] tests/intel/xe_exec_threads: separate exec_sync and batch buffer fei.yang
2024-11-12 13:23   ` Nirmoy Das
2024-11-08  1:48 ` ✓ Fi.CI.BAT: success for separate sync data and batch buffer (rev2) Patchwork
2024-11-08  1:50 ` ✗ CI.xeBAT: failure " Patchwork
2024-11-08  4:44 ` ✗ Fi.CI.IGT: " Patchwork
2024-11-09  8:40 ` ✗ CI.xeFULL: " 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=20241108011041.2257553-4-fei.yang@intel.com \
    --to=fei.yang@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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.