From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Print GuC queue submission state on engine reset
Date: Fri, 19 Dec 2025 11:09:11 -0500 [thread overview]
Message-ID: <aUV4p3hqylrR2hk4@intel.com> (raw)
In-Reply-To: <20251218224546.4057424-1-matthew.brost@intel.com>
On Thu, Dec 18, 2025 at 02:45:46PM -0800, Matthew Brost wrote:
> Print the GuC queue submission state when an engine reset occurs, as
> this provides clues about the cause of the reset.
>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc_submit.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
> index 259c4e1dcae7..0b590271c326 100644
> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> @@ -3080,8 +3080,9 @@ int xe_guc_exec_queue_reset_handler(struct xe_guc *guc, u32 *msg, u32 len)
> if (unlikely(!q))
> return -EPROTO;
>
> - xe_gt_info(gt, "Engine reset: engine_class=%s, logical_mask: 0x%x, guc_id=%d",
> - xe_hw_engine_class_to_str(q->class), q->logical_mask, guc_id);
> + xe_gt_info(gt, "Engine reset: engine_class=%s, logical_mask: 0x%x, guc_id=%d, state=0x%0x",
> + xe_hw_engine_class_to_str(q->class), q->logical_mask, guc_id,
> + atomic_read(&q->guc->state));
>
> trace_xe_exec_queue_reset(q);
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-12-19 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 22:45 [PATCH] drm/xe: Print GuC queue submission state on engine reset Matthew Brost
2025-12-19 3:21 ` ✓ CI.KUnit: success for " Patchwork
2025-12-19 3:57 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-19 16:09 ` Rodrigo Vivi [this message]
2025-12-20 7:25 ` ✗ 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=aUV4p3hqylrR2hk4@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--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