From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: jose.souza@intel.com, lionel.g.landwerlin@intel.com,
carlos.santa@intel.com, rodrigo.vivi@intel.com
Subject: [RFC PATCH 0/6] Add support for Mesa GPU hang replay tool
Date: Wed, 22 Jan 2025 17:15:07 -0800 [thread overview]
Message-ID: <20250123011513.362430-1-matthew.brost@intel.com> (raw)
Add support for the Mesa GPU hang replay tool, which exists in the i915.
The main changes are as follows:
- Update devcoredump to include additional information, allowing the
Mesa tool to extract everything it needs to replay a GPU hang. These
updates are designed to remain compatible with the existing Mesa
devcoredump parser.
- Introduce the DRM_XE_EXEC_QUEUE_SET_HANG_REPLAY_STATE extension, which
enables setting the execution queue state to the hung execution queue
state.
This is being sent as an RFC, as the Mesa uAPI tool has yet to be developed. The tool is a prerequisite for merging this change.
Matt
Matthew Brost (6):
drm/xe: Add properties line to VM snapshot capture
drm/xe: Add "null_sparse" type to VM snap properties
drm/xe: Add mem_region to properties line in VM snapshot capture
drm/xe/uapi: Add DRM_XE_EXEC_QUEUE_SET_HANG_REPLAY_STATE
drm/xe: Add replay_offset and replay_length lines to LRC HWCTX
snapshot
drm/xe: Implement DRM_XE_EXEC_QUEUE_SET_HANG_REPLAY_STATE
drivers/gpu/drm/xe/xe_exec_queue.c | 29 +++++++++++++++-
drivers/gpu/drm/xe/xe_exec_queue_types.h | 3 ++
drivers/gpu/drm/xe/xe_execlist.c | 2 +-
drivers/gpu/drm/xe/xe_lrc.c | 40 ++++++++++++++++++----
drivers/gpu/drm/xe/xe_lrc.h | 4 ++-
drivers/gpu/drm/xe/xe_lrc_types.h | 3 ++
drivers/gpu/drm/xe/xe_vm.c | 42 +++++++++++++++++++++++-
include/uapi/drm/xe_drm.h | 9 +++--
8 files changed, 120 insertions(+), 12 deletions(-)
--
2.34.1
next reply other threads:[~2025-01-23 1:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 1:15 Matthew Brost [this message]
2025-01-23 1:15 ` [RFC PATCH 1/6] drm/xe: Add properties line to VM snapshot capture Matthew Brost
2025-01-23 17:38 ` Matthew Brost
2025-01-23 1:15 ` [RFC PATCH 2/6] drm/xe: Add "null_sparse" type to VM snap properties Matthew Brost
2025-01-23 1:15 ` [RFC PATCH 3/6] drm/xe: Add mem_region to properties line in VM snapshot capture Matthew Brost
2025-01-23 1:15 ` [RFC PATCH 4/6] drm/xe/uapi: Add DRM_XE_EXEC_QUEUE_SET_HANG_REPLAY_STATE Matthew Brost
2025-01-23 10:36 ` Rodrigo Vivi
2025-01-23 17:37 ` Matthew Brost
2025-01-23 1:15 ` [RFC PATCH 5/6] drm/xe: Add replay_offset and replay_length lines to LRC HWCTX snapshot Matthew Brost
2025-01-23 1:15 ` [RFC PATCH 6/6] drm/xe: Implement DRM_XE_EXEC_QUEUE_SET_HANG_REPLAY_STATE Matthew Brost
2025-01-23 17:40 ` Matthew Brost
2025-01-23 1:24 ` ✓ CI.Patch_applied: success for Add support for Mesa GPU hang replay tool Patchwork
2025-01-23 1:24 ` ✓ CI.checkpatch: " Patchwork
2025-01-23 1:25 ` ✓ CI.KUnit: " Patchwork
2025-01-23 1:42 ` ✓ CI.Build: " Patchwork
2025-01-23 1:44 ` ✓ CI.Hooks: " Patchwork
2025-01-23 1:46 ` ✓ CI.checksparse: " Patchwork
2025-01-23 2:12 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-23 13:03 ` ✗ Xe.CI.Full: failure " 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=20250123011513.362430-1-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=carlos.santa@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=lionel.g.landwerlin@intel.com \
--cc=rodrigo.vivi@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