From: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
To: Stuart Summers <stuart.summers@intel.com>
Cc: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t 1/3] tests/intel/xe_exec_reset: Add a comment about return for syncobj wait
Date: Sun, 12 Apr 2026 19:29:49 -0700 [thread overview]
Message-ID: <adxVHTOVXhsrydLn@nvishwa1-desk> (raw)
In-Reply-To: <20260409203702.4350-2-stuart.summers@intel.com>
On Thu, Apr 09, 2026 at 08:36:59PM +0000, Stuart Summers wrote:
>Add a comment to the syncobj wait after a hanging submission
>to indicate that even for the hang case, we expect the syncobj
>wait to return successfully as opposed to the wait ufence case
>where we only return successful if hardware did in fact execute
>the batch through the MI_USER_INTERRUPT to satisfy the wait ufence.
>
>Signed-off-by: Stuart Summers <stuart.summers@intel.com>
>---
> lib/xe/xe_legacy.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
>diff --git a/lib/xe/xe_legacy.c b/lib/xe/xe_legacy.c
>index 084445305..6aeddc578 100644
>--- a/lib/xe/xe_legacy.c
>+++ b/lib/xe/xe_legacy.c
>@@ -181,8 +181,13 @@ xe_legacy_test_mode(int fd, struct drm_xe_engine_class_instance *eci,
> return;
> }
>
>- for (i = 0; i < n_exec_queues && n_execs; i++)
>+ for (i = 0; i < n_exec_queues && n_execs; i++) {
>+ /*
>+ * Expectation here is that on reset, submissions will
>+ * still satisfy the syncobj_wait.
>+ */
> igt_assert(syncobj_wait(fd, &syncobjs[i], 1, INT64_MAX, 0, NULL));
>+ }
>
> igt_assert(syncobj_wait(fd, &sync[0].handle, 1, INT64_MAX, 0, NULL));
>
LGTM
Reviewed-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
>--
>2.43.0
>
next prev parent reply other threads:[~2026-04-13 2:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 20:36 [PATCH i-g-t 0/3] Add test coverage for multi queue reset Stuart Summers
2026-04-09 20:36 ` [PATCH i-g-t 1/3] tests/intel/xe_exec_reset: Add a comment about return for syncobj wait Stuart Summers
2026-04-13 2:29 ` Niranjana Vishwanathapura [this message]
2026-04-09 20:37 ` [PATCH i-g-t 2/3] tests/intel/xe_exec_reset: Add checks for hanging queue wait_ufence return Stuart Summers
2026-04-13 2:30 ` Niranjana Vishwanathapura
2026-04-09 20:37 ` [PATCH i-g-t 3/3] tests/intel/xe_exec_reset: Add multi queue subtests Stuart Summers
2026-04-13 2:32 ` Niranjana Vishwanathapura
2026-04-13 21:00 ` Summers, Stuart
2026-04-13 2:34 ` Niranjana Vishwanathapura
2026-04-13 21:01 ` Summers, Stuart
2026-04-13 21:17 ` Summers, Stuart
2026-04-10 4:15 ` ✓ Xe.CI.BAT: success for Add test coverage for multi queue reset Patchwork
2026-04-10 4:29 ` ✓ i915.CI.BAT: " Patchwork
2026-04-10 9:54 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-13 21:02 ` Summers, Stuart
2026-04-11 0:11 ` ✗ 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=adxVHTOVXhsrydLn@nvishwa1-desk \
--to=niranjana.vishwanathapura@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=stuart.summers@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