From: Matthew Brost <matthew.brost@intel.com>
To: Jonathan Cavitt <jonathan.cavitt@intel.com>
Cc: <igt-dev@lists.freedesktop.org>, <saurabhg.gupta@intel.com>,
<john.c.harrison@intel.com>, <stuart.summers@intel.com>
Subject: Re: [PATCH i-g-t v4 2/2] test/intel/xe_exec_reset: Synchronize cm-gt-reset gt resets
Date: Wed, 5 Jun 2024 18:20:20 +0000 [thread overview]
Message-ID: <ZmCsZK8ccLbqcUvO@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20240605175843.2789838-3-jonathan.cavitt@intel.com>
On Wed, Jun 05, 2024 at 10:58:43AM -0700, Jonathan Cavitt wrote:
> The cm-gt-reset test has the potential to race with itself on the gt
> reset, so force the gt reset to be synchronous here. The race condition
> occurs because the test does not have a fencing mechanism (I.E.
> dma-fence) to protect against this race, unlike in the gt-reset test
> case, for example.
>
> Suggested-by: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> CC: John Harrison <john.c.harrison@intel.com>
> CC: Stuart Summers <stuart.summers@intel.com>
> ---
> tests/intel/xe_exec_reset.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/intel/xe_exec_reset.c b/tests/intel/xe_exec_reset.c
> index 05d63c0ba5..817b82cdef 100644
> --- a/tests/intel/xe_exec_reset.c
> +++ b/tests/intel/xe_exec_reset.c
> @@ -530,7 +530,7 @@ test_compute_mode(int fd, struct drm_xe_engine_class_instance *eci,
> }
>
> if (flags & GT_RESET)
> - xe_force_gt_reset_async(fd, eci->gt_id);
> + xe_force_gt_reset_sync(fd, eci->gt_id);
>
> if (flags & CLOSE_FD) {
> if (flags & CLOSE_EXEC_QUEUES) {
> --
> 2.25.1
>
next prev parent reply other threads:[~2024-06-05 18:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 17:58 [PATCH i-g-t v4 0/2] lib/xe: Use synchronous gt resets when needed Jonathan Cavitt
2024-06-05 17:58 ` [PATCH i-g-t v4 1/2] lib/xe: Add sync and async xe_force_gt_reset options Jonathan Cavitt
2024-06-05 18:19 ` Matthew Brost
2024-06-05 17:58 ` [PATCH i-g-t v4 2/2] test/intel/xe_exec_reset: Synchronize cm-gt-reset gt resets Jonathan Cavitt
2024-06-05 18:20 ` Matthew Brost [this message]
2024-06-05 18:57 ` ✓ CI.xeBAT: success for lib/xe: Use synchronous gt resets when needed (rev4) Patchwork
2024-06-05 19:05 ` ✓ Fi.CI.BAT: " Patchwork
2024-06-06 0:57 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-06-06 9:36 ` ✓ CI.xeFULL: success " Patchwork
2024-06-07 19:06 ` ✗ GitLab.Pipeline: warning " 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=ZmCsZK8ccLbqcUvO@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=john.c.harrison@intel.com \
--cc=jonathan.cavitt@intel.com \
--cc=saurabhg.gupta@intel.com \
--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