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 v3 0/4] Track FAST_REQ H2Gs to report where errors came from
Date: Wed,  7 May 2025 18:34:33 -0700	[thread overview]
Message-ID: <20250508013437.652982-1-John.C.Harrison@Intel.com> (raw)

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

Most H2G messages are FAST_REQ which means no synchronous response is
expected. However, errors can still be returned. Add support for
tracking the FAST_REQ H2Gs and matching up an error response to its
originator.

v2: Split RESPONSE define into separate patch, re-word
comments/prints, fix consistency of conditional compilation (review
feedback from Daniele & Michal W).
v3: Split into more patches, add more RESPONSE defines, improve
debug print message (review feedback from Michal W).

Signed-off-by: John Harrison <John.C.Harrison@Intel.com>


John Harrison (4):
  drm/xe/guc: Remove double blank line
  drm/xe/guc: Add missing H2G error code definitions
  drm/xe/guc: Rename CONFIG_XE_LARGE_GUC_BUFFER
  drm/xe/guc: Track FAST_REQ H2Gs to report where errors came from

 drivers/gpu/drm/xe/Kconfig.debug        |  11 ++-
 drivers/gpu/drm/xe/abi/guc_errors_abi.h |  15 ++-
 drivers/gpu/drm/xe/xe_guc_ct.c          | 117 ++++++++++++++++++++----
 drivers/gpu/drm/xe/xe_guc_ct_types.h    |  15 +++
 drivers/gpu/drm/xe/xe_guc_log.h         |   2 +-
 5 files changed, 133 insertions(+), 27 deletions(-)

-- 
2.49.0


             reply	other threads:[~2025-05-08  1:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08  1:34 John.C.Harrison [this message]
2025-05-08  1:34 ` [PATCH v3 1/4] drm/xe/guc: Remove double blank line John.C.Harrison
2025-05-08 19:37   ` Michal Wajdeczko
2025-05-08  1:34 ` [PATCH v3 2/4] drm/xe/guc: Add missing H2G error code definitions John.C.Harrison
2025-05-08 19:50   ` Michal Wajdeczko
2025-05-12 19:30     ` John Harrison
2025-05-08  1:34 ` [PATCH v3 3/4] drm/xe/guc: Rename CONFIG_XE_LARGE_GUC_BUFFER John.C.Harrison
2025-05-08 19:52   ` Michal Wajdeczko
2025-05-08  1:34 ` [PATCH v3 4/4] drm/xe/guc: Track FAST_REQ H2Gs to report where errors came from John.C.Harrison
2025-05-08 20:11   ` Michal Wajdeczko
2025-05-12 19:52     ` John Harrison
2025-05-08  1:40 ` ✓ CI.Patch_applied: success for Track FAST_REQ H2Gs to report where errors came from (rev2) Patchwork
2025-05-08  1:40 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-08  1:41 ` ✓ CI.KUnit: success " Patchwork
2025-05-08  1:50 ` ✓ CI.Build: " Patchwork
2025-05-08  1:52 ` ✓ CI.Hooks: " Patchwork
2025-05-08  1:53 ` ✓ CI.checksparse: " Patchwork
2025-05-08  2:15 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-08 22:58 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-26 18:39 ` ✗ CI.Patch_applied: " 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=20250508013437.652982-1-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