From: Arvind Yadav <arvind.yadav@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: rodrigo.vivi@intel.com, badal.nilawar@intel.com,
michal.wajdeczko@intel.com, himal.prasad.ghimiray@intel.com,
dnyaneshwar.bhadane@intel.com, mallesh.koujalagi@intel.com,
matthew.brost@intel.com
Subject: [PATCH v7 0/4] drm/xe: Report GT TDR and VM rebind faults using SIGID
Date: Thu, 3 Sep 2026 11:16:06 +0530 [thread overview]
Message-ID: <20260903054610.3640788-1-arvind.yadav@intel.com> (raw)
This series is a small follow-up on top of the structured SIGID error
logging infrastructure series:
https://patchwork.freedesktop.org/series/171022/
That series adds SIGID-based error reporting and the xe_log_*() helpers.
This series converts selected GuC submission, SVM page-fault and GT reset
error paths to that logging path.
The VM rebind conversion from earlier revisions remains dropped.
v7:
- Updated the GUCSUBMIT commit message.
- Updated GuC submission wording.
- Added a GRDOM_RESET_TIMEOUT_MS constant for GT reset timeout.
v6:
- Moved GUCSUBMIT from DRIVER_FIRMWARE to DRIVER, since GuC submit
is a driver submission component and not a firmware component.
(Michal)
- Updated the log message to print class/instance as %u:%u and
reason as %#x. (Michal)
v5:
- Dropped the GuC CGP protocol SIGID conversion, since malformed G2H
handler errors are already reported by the CT layer after -EPROTO.
- Added a GUCSUBMIT component mapped to XE_SIGID_GT_TDR and used it for
the GuC submit reset failure.
- Dropped "request" from the GuC submit reset failure message.
- Kept the GT patch limited to the reset failure path.
- Dropped GT PM-flow SIGID conversions for now, since the correct
component/SIGID mapping needs agreement.
- Improved the GT reset failure message to describe that full graphics
reset did not complete.
v4:
- Clarified that the GT component maps to XE_SIGID_GT_TDR and -EIO is
only the errno value.
- Split GuC CGP protocol error conversions into a separate patch.
- Added terminal SVM page-fault allocation failures as MEM_FAULT reports.
- Converted GT reset and power-flow failures to GT_TDR reports.
- Kept the VM rebind conversion dropped.
v3:
- Split GuC and VM changes into separate patches.
- Dropped GuC job-timeout warning conversions to avoid changing warning
logs into error-level SIGID reports.
v2:
- Rebased on the latest structured SIGID logging series.
- Switched from the old xe_ras_log_*() helpers to the new xe_log_*()
helpers.
Arvind Yadav (4):
drm/xe/log: Add GUCSUBMIT component
drm/xe/guc: Report reset failure using SIGID
drm/xe/svm: Report terminal page-fault failures using SIGID
drm/xe/gt: Report GT reset failure using SIGID
drivers/gpu/drm/xe/abi/xe_log_abi.h | 1 +
drivers/gpu/drm/xe/xe_gt.c | 11 ++++++++---
drivers/gpu/drm/xe/xe_guc_submit.c | 6 ++++--
drivers/gpu/drm/xe/xe_svm.c | 13 +++++++------
4 files changed, 20 insertions(+), 11 deletions(-)
--
2.43.0
next reply other threads:[~2026-09-03 5:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 5:46 Arvind Yadav [this message]
2026-09-03 5:46 ` [PATCH v7 1/4] drm/xe/log: Add GUCSUBMIT component Arvind Yadav
2026-09-03 5:46 ` [PATCH v7 2/4] drm/xe/guc: Report reset failure using SIGID Arvind Yadav
2026-09-03 5:46 ` [PATCH v7 3/4] drm/xe/svm: Report terminal page-fault failures " Arvind Yadav
2026-09-03 5:46 ` [PATCH v7 4/4] drm/xe/gt: Report GT reset failure " Arvind Yadav
2026-09-03 5:54 ` ✓ CI.KUnit: success for drm/xe: Report GT TDR and VM rebind faults using SIGID (rev7) Patchwork
2026-09-03 6:32 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-03 18:05 ` ✗ 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=20260903054610.3640788-1-arvind.yadav@intel.com \
--to=arvind.yadav@intel.com \
--cc=badal.nilawar@intel.com \
--cc=dnyaneshwar.bhadane@intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=mallesh.koujalagi@intel.com \
--cc=matthew.brost@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=rodrigo.vivi@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