Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Nirmoy Das <nirmoy.das@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Add engine name to the engine reset and cat-err log
Date: Thu, 25 Apr 2024 20:31:27 +0000	[thread overview]
Message-ID: <Ziq9n0f24pKHCQTN@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <e2c55678-55f8-4ee8-9be9-f941f29f7724@intel.com>

On Thu, Apr 25, 2024 at 09:11:22PM +0200, Nirmoy Das wrote:
> Hi Matt,
> 
> On 4/25/2024 7:46 PM, Matthew Brost wrote:
> > On Thu, Apr 25, 2024 at 02:18:56PM +0200, Nirmoy Das wrote:
> > > Add engine name to the engine reset and cat error log
> > > which should be useful while debugging.
> > > 
> > > Signed-off-by: Nirmoy Das <nirmoy.das@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 c7d38469fb46..245e29d095c0 100644
> > > --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> > > +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> > > @@ -1655,7 +1655,7 @@ int xe_guc_exec_queue_reset_handler(struct xe_guc *guc, u32 *msg, u32 len)
> > >   	if (unlikely(!q))
> > >   		return -EPROTO;
> > > -	drm_info(&xe->drm, "Engine reset: guc_id=%d", guc_id);
> > > +	drm_info(&xe->drm, "Engine reset: name=%s, guc_id=%d", q->hwe->name, guc_id);
> > I don't think q->hwe->name name is useful as it might not actually be
> > exec queue is running. I'd drop that, and replace with string indicating
> > the hardware engine class.
> 
> I will resend with engine class instead.
> 

Maybe include the logical mask of exec queue too.

Matt

> Thanks,
> 
> Nirmoy
> 
> > >   	/* FIXME: Do error capture, most likely async */
> > > @@ -1690,7 +1690,8 @@ int xe_guc_exec_queue_memory_cat_error_handler(struct xe_guc *guc, u32 *msg,
> > >   	if (unlikely(!q))
> > >   		return -EPROTO;
> > > -	drm_dbg(&xe->drm, "Engine memory cat error: guc_id=%d", guc_id);
> > > +	drm_dbg(&xe->drm, "Engine memory cat error: name=%s, guc_id=%d",
> > > +		q->hwe->name, guc_id);
> > Same here.
> > 
> > Matt
> > 
> > >   	trace_xe_exec_queue_memory_cat_error(q);
> > >   	/* Treat the same as engine reset */
> > > -- 
> > > 2.42.0
> > > 

  reply	other threads:[~2024-04-25 20:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 12:18 [PATCH] drm/xe: Add engine name to the engine reset and cat-err log Nirmoy Das
2024-04-25 13:05 ` ✓ CI.Patch_applied: success for " Patchwork
2024-04-25 13:06 ` ✓ CI.checkpatch: " Patchwork
2024-04-25 13:07 ` ✓ CI.KUnit: " Patchwork
2024-04-25 13:18 ` ✓ CI.Build: " Patchwork
2024-04-25 13:21 ` ✓ CI.Hooks: " Patchwork
2024-04-25 13:22 ` ✓ CI.checksparse: " Patchwork
2024-04-25 13:53 ` ✓ CI.BAT: " Patchwork
2024-04-25 17:46 ` [PATCH] " Matthew Brost
2024-04-25 19:11   ` Nirmoy Das
2024-04-25 20:31     ` Matthew Brost [this message]
2024-04-25 21:16       ` Nirmoy Das
2024-04-29 21:17         ` John Harrison
2024-04-30  3:28           ` Matthew Brost
2024-04-25 19:15   ` Michal Wajdeczko
2024-04-25 20:30     ` Matthew Brost
2024-04-25 21:17     ` Nirmoy Das
2024-04-26  3:12 ` ✓ CI.FULL: success for " 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=Ziq9n0f24pKHCQTN@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=nirmoy.das@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