From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <jose.souza@intel.com>,
<lionel.g.landwerlin@intel.com>, <carlos.santa@intel.com>
Subject: Re: [RFC PATCH 4/6] drm/xe/uapi: Add DRM_XE_EXEC_QUEUE_SET_HANG_REPLAY_STATE
Date: Thu, 23 Jan 2025 05:36:07 -0500 [thread overview]
Message-ID: <Z5Ibl_Lc_wyFeV8C@intel.com> (raw)
In-Reply-To: <20250123011513.362430-5-matthew.brost@intel.com>
On Wed, Jan 22, 2025 at 05:15:11PM -0800, Matthew Brost wrote:
> Add DRM_XE_EXEC_QUEUE_SET_HANG_REPLAY_STATE which accepts a user pointer
> to populate the exec queue state so that a GPU hang can be replayed via
> a Mesa tool.
>
> Cc: José Roberto de Souza <jose.souza@intel.com>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> ---
> include/uapi/drm/xe_drm.h | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h
> index e2160330ad01..0fe8c2e8b022 100644
> --- a/include/uapi/drm/xe_drm.h
> +++ b/include/uapi/drm/xe_drm.h
> @@ -204,8 +204,12 @@ struct drm_xe_ext_set_property {
> /** @pad: MBZ */
> __u32 pad;
>
> - /** @value: property value */
> - __u64 value;
> + union {
> + /** @value: property value */
> + __u64 value;
> + /** @ptr: pointer to user value */
> + __u64 ptr;
> + };
>
> /** @reserved: Reserved */
> __u64 reserved[2];
> @@ -1137,6 +1141,7 @@ struct drm_xe_exec_queue_create {
> #define DRM_XE_EXEC_QUEUE_EXTENSION_SET_PROPERTY 0
> #define DRM_XE_EXEC_QUEUE_SET_PROPERTY_PRIORITY 0
> #define DRM_XE_EXEC_QUEUE_SET_PROPERTY_TIMESLICE 1
> +#define DRM_XE_EXEC_QUEUE_SET_HANG_REPLAY_STATE 2
Will mesa need a property to read and know that this is supported by the
running kernel?
>
> /** @extensions: Pointer to the first extension struct, if any */
> __u64 extensions;
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-01-23 10:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 1:15 [RFC PATCH 0/6] Add support for Mesa GPU hang replay tool Matthew Brost
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 [this message]
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=Z5Ibl_Lc_wyFeV8C@intel.com \
--to=rodrigo.vivi@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=matthew.brost@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