From: Jonathan Cavitt <jonathan.cavitt@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: jonathan.cavitt@intel.com, saurabhg.gupta@intel.com,
matthew.brost@intel.com, john.c.harrison@intel.com,
stuart.summers@intel.com
Subject: [PATCH i-g-t v4 0/2] lib/xe: Use synchronous gt resets when needed
Date: Wed, 5 Jun 2024 10:58:41 -0700 [thread overview]
Message-ID: <20240605175843.2789838-1-jonathan.cavitt@intel.com> (raw)
Add a new xe_force_gt_reset function, xe_force_gt_reset_sync, renaming
the original xe_force_gt_reset to xe_force_gt_reset_async. This allows
the user to decide whether or not they want to initiate a synchronous or
asynchronous gt reset. The asynchronous reset function was otherwise
unchanged, but the synchronous reset function operates by calling a new
debugfs function.
Tests will use the asynchronous gt reset function by default, but the
test xe_exec_reset@cm-gt-reset will want to use the synchronous version
because it lacks a blocking mechanism on the reset and may race with
itself otherwise.
v2:
- Create a new function for synchronous gt reset instead of using a tag
to denote between the two modes (Matthew Brost)
v3:
- Fix compile issue
v4:
- Use helper function for xe_force_gt_reset_[sync|async] functions to
reduce code duplication (Matthew Brost)
- Add missing revision notes
Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/1068
Test-with: 20240605150828.2736396-1-jonathan.cavitt@intel.com
Suggested-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>
Jonathan Cavitt (2):
lib/xe: Add sync and async xe_force_gt_reset options
test/intel/xe_exec_reset: Synchronize cm-gt-reset gt resets
lib/xe/xe_gt.c | 2 +-
lib/xe/xe_ioctl.c | 16 +++++++++++++---
lib/xe/xe_ioctl.h | 3 ++-
tests/intel/xe_exec_reset.c | 8 ++++----
tests/intel/xe_gt_freq.c | 2 +-
tests/intel/xe_wedged.c | 2 +-
6 files changed, 22 insertions(+), 11 deletions(-)
--
2.25.1
next reply other threads:[~2024-06-05 18:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 17:58 Jonathan Cavitt [this message]
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
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=20240605175843.2789838-1-jonathan.cavitt@intel.com \
--to=jonathan.cavitt@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=john.c.harrison@intel.com \
--cc=matthew.brost@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