Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: "Cavitt, Jonathan" <jonathan.cavitt@intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v5 06/10] drm/xe: Improve unexpected state error messages
Date: Mon, 10 Jun 2024 17:09:02 +0000	[thread overview]
Message-ID: <ZmczLiGEnTFHIyE7@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <1ec633a8-4a2f-435f-9159-4c8d48c1d931@intel.com>

On Mon, Jun 10, 2024 at 06:45:12PM +0200, Michal Wajdeczko wrote:
> 
> 
> On 10.06.2024 18:36, Cavitt, Jonathan wrote:
> > -----Original Message-----
> > From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf Of Matthew Brost
> > Sent: Monday, June 10, 2024 7:18 AM
> > To: intel-xe@lists.freedesktop.org
> > Subject: [PATCH v5 06/10] drm/xe: Improve unexpected state error messages
> >>
> >> Include G2H handler name when an unexpected error state messages.
> >>
> >> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> > 
> > Having a separation for these two error messages is a good idea.
> > Reviewed-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> > -Jonathan Cavitt
> > 
> >> ---
> >>  drivers/gpu/drm/xe/xe_guc_submit.c | 8 ++++----
> >>  1 file changed, 4 insertions(+), 4 deletions(-)
> >>
> >> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
> >> index 4464ba337d12..766ff8e48dde 100644
> >> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> >> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> >> @@ -1632,8 +1632,8 @@ int xe_guc_sched_done_handler(struct xe_guc *guc, u32 *msg, u32 len)
> >>  
> >>  	if (unlikely(!exec_queue_pending_enable(q) &&
> >>  		     !exec_queue_pending_disable(q))) {
> >> -		drm_err(&xe->drm, "Unexpected engine state 0x%04x",
> >> -			atomic_read(&q->guc->state));
> >> +		drm_err(&xe->drm, "SCHED_DONE: Unexpected engine state 0x%04x, guc_id=%d",
> >> +			atomic_read(&q->guc->state), q->guc->id);
> 
> but please at least use xe_gt_err()
> 

I think I'll just switch to xe_gt_err in next rev or at merge time.

Matt

> other option would be to use xe_gt_err_printer() and dump engine state
> in more friendly/detailed way
> 
> >>  		return -EPROTO;
> >>  	}
> >>  
> >> @@ -1671,8 +1671,8 @@ int xe_guc_deregister_done_handler(struct xe_guc *guc, u32 *msg, u32 len)
> >>  
> >>  	if (!exec_queue_destroyed(q) || exec_queue_pending_disable(q) ||
> >>  	    exec_queue_pending_enable(q) || exec_queue_enabled(q)) {
> >> -		drm_err(&xe->drm, "Unexpected engine state 0x%04x",
> >> -			atomic_read(&q->guc->state));
> >> +		drm_err(&xe->drm, "DEREGISTER_DONE: Unexpected engine state 0x%04x, guc_id=%d",
> >> +			atomic_read(&q->guc->state), q->guc->id);
> 
> ditto
> 
> >>  		return -EPROTO;
> >>  	}
> >>  
> >> -- 
> >> 2.34.1
> >>
> >>

  reply	other threads:[~2024-06-10 17:09 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10 14:18 [PATCH v5 00/10] Only timeout jobs if they run longer than timeout period Matthew Brost
2024-06-10 14:18 ` [PATCH v5 01/10] drm/xe: Add LRC ctx timestamp support functions Matthew Brost
2024-06-10 17:32   ` Cavitt, Jonathan
2024-06-10 14:18 ` [PATCH v5 02/10] drm/xe: Add MI_COPY_MEM_MEM GPU instruction definitions Matthew Brost
2024-06-10 16:39   ` Cavitt, Jonathan
2024-06-10 14:18 ` [PATCH v5 03/10] drm/xe: Emit ctx timestamp copy in ring ops Matthew Brost
2024-06-10 14:44   ` Cavitt, Jonathan
2024-06-10 14:18 ` [PATCH v5 04/10] drm/xe: Add ctx timestamp to LRC snapshot Matthew Brost
2024-06-10 16:40   ` Cavitt, Jonathan
2024-06-10 14:18 ` [PATCH v5 05/10] drm/xe: Add xe_gt_clock_interval_to_ms helper Matthew Brost
2024-06-10 16:34   ` Cavitt, Jonathan
2024-06-12 12:09     ` Ghimiray, Himal Prasad
2024-06-10 14:18 ` [PATCH v5 06/10] drm/xe: Improve unexpected state error messages Matthew Brost
2024-06-10 16:36   ` Cavitt, Jonathan
2024-06-10 16:45     ` Michal Wajdeczko
2024-06-10 17:09       ` Matthew Brost [this message]
2024-06-11  0:09   ` John Harrison
2024-06-11  1:43     ` Matthew Brost
2024-06-10 14:18 ` [PATCH v5 07/10] drm/xe: Add GuC state asserts to deregister_exec_queue Matthew Brost
2024-06-10 17:12   ` Cavitt, Jonathan
2024-06-10 14:18 ` [PATCH v5 08/10] drm/xe: Add pending disable assert to handle_sched_done Matthew Brost
2024-06-10 16:35   ` Cavitt, Jonathan
2024-06-10 14:18 ` [PATCH v5 09/10] drm/xe: Add killed, banned, or wedged as stick bit during GuC reset Matthew Brost
2024-06-10 16:35   ` Cavitt, Jonathan
2024-06-10 14:18 ` [PATCH v5 10/10] drm/xe: Sample ctx timestamp to determine if jobs have timed out Matthew Brost
2024-06-10 19:32   ` Cavitt, Jonathan
2024-06-10 20:12     ` Matthew Brost
2024-06-11  0:36   ` John Harrison
2024-06-11  1:35     ` Matthew Brost
2024-06-12  4:21   ` Zbigniew Kempczyński
2024-06-10 14:23 ` ✓ CI.Patch_applied: success for Only timeout jobs if they run longer than timeout period Patchwork
2024-06-10 14:23 ` ✗ CI.checkpatch: warning " Patchwork
2024-06-10 14:24 ` ✓ CI.KUnit: success " Patchwork
2024-06-10 14:36 ` ✓ CI.Build: " Patchwork
2024-06-10 14:38 ` ✗ CI.Hooks: failure " Patchwork
2024-06-10 14:39 ` ✓ CI.checksparse: success " Patchwork
2024-06-10 15:16 ` ✓ CI.BAT: " 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=ZmczLiGEnTFHIyE7@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jonathan.cavitt@intel.com \
    --cc=michal.wajdeczko@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