Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John.C.Harrison@Intel.com
To: Intel-Xe@Lists.FreeDesktop.Org
Cc: John Harrison <John.C.Harrison@Intel.com>
Subject: [PATCH 1/2] drm/xe/guc: Add a missing H2G error code definition
Date: Wed, 26 Mar 2025 12:32:38 -0700	[thread overview]
Message-ID: <20250326193240.4165833-2-John.C.Harrison@Intel.com> (raw)
In-Reply-To: <20250326193240.4165833-1-John.C.Harrison@Intel.com>

From: John Harrison <John.C.Harrison@Intel.com>

These error codes are not actually used in the driver but it is
extremely useful to have them available to understand error messages.
The most recent spate of FAST_REQ errors being reported have been
about error 0x30C, so add in the missing define for that.

Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
---
 drivers/gpu/drm/xe/abi/guc_errors_abi.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/gpu/drm/xe/abi/guc_errors_abi.h b/drivers/gpu/drm/xe/abi/guc_errors_abi.h
index 2c627a21648f..c25ea52a6e61 100644
--- a/drivers/gpu/drm/xe/abi/guc_errors_abi.h
+++ b/drivers/gpu/drm/xe/abi/guc_errors_abi.h
@@ -40,6 +40,7 @@ enum xe_guc_response_status {
 	XE_GUC_RESPONSE_CTB_NOT_REGISTERED                  = 0x304,
 	XE_GUC_RESPONSE_CTB_IN_USE                          = 0x305,
 	XE_GUC_RESPONSE_CTB_INVALID_DESC                    = 0x306,
+	XE_GUC_RESPONSE_STATUS_HW_TIMEOUT                   = 0x30C,
 	XE_GUC_RESPONSE_CTB_SOURCE_INVALID_DESCRIPTOR       = 0x30D,
 	XE_GUC_RESPONSE_CTB_DESTINATION_INVALID_DESCRIPTOR  = 0x30E,
 	XE_GUC_RESPONSE_INVALID_CONFIG_STATE                = 0x30F,
-- 
2.49.0


  reply	other threads:[~2025-03-26 19:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 19:32 [PATCH 0/2] Track FAST_REQ H2Gs to report where errors came from John.C.Harrison
2025-03-26 19:32 ` John.C.Harrison [this message]
2025-04-23  8:51   ` [PATCH 1/2] drm/xe/guc: Add a missing H2G error code definition Michal Wajdeczko
2025-03-26 19:32 ` [PATCH 2/2] drm/xe/guc: Track FAST_REQ H2Gs to report where errors came from John.C.Harrison
2025-04-23  9:18   ` Michal Wajdeczko
2025-03-26 20:07 ` ✓ CI.Patch_applied: success for " Patchwork
2025-03-26 20:07 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-26 20:08 ` ✓ CI.KUnit: success " Patchwork
2025-03-26 20:25 ` ✓ CI.Build: " Patchwork
2025-03-26 20:27 ` ✓ CI.Hooks: " Patchwork
2025-03-26 20:29 ` ✓ CI.checksparse: " Patchwork
2025-03-26 20:51 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-27 12:30 ` ✗ 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=20250326193240.4165833-2-John.C.Harrison@Intel.com \
    --to=john.c.harrison@intel.com \
    --cc=Intel-Xe@Lists.FreeDesktop.Org \
    /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