From: Raag Jadav <raag.jadav@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: matthew.brost@intel.com, rodrigo.vivi@intel.com,
riana.tauro@intel.com, michal.wajdeczko@intel.com,
matthew.d.roper@intel.com, umesh.nerlige.ramappa@intel.com,
mallesh.koujalagi@intel.com, Raag Jadav <raag.jadav@intel.com>
Subject: [PATCH v2 0/4] Hardware Error handling for Crescent Island
Date: Thu, 2 Apr 2026 23:12:25 +0530 [thread overview]
Message-ID: <20260402174229.1062874-1-raag.jadav@intel.com> (raw)
This series sets up hardware error routing for debug cases on Crescent
Island and handles them by wedging the device so that they are available
to the user for debugging.
v2: Explain the usecase (Matt Roper)
Allow hardware error routing through debugfs (Mallesh)
Raag Jadav (4):
drm/xe/hw_error: Setup hardware error routing
drm/xe/hw_error: Reuse CSC worker for generic error handling
drm/xe/hw_error: Allow debugging hardware errors
drm/xe/debugfs: Update hardware error routing with wedged.mode
drivers/gpu/drm/xe/regs/xe_hw_error_regs.h | 5 ++
drivers/gpu/drm/xe/xe_debugfs.c | 2 +
drivers/gpu/drm/xe/xe_hw_error.c | 55 ++++++++++++++++++----
drivers/gpu/drm/xe/xe_hw_error.h | 1 +
drivers/gpu/drm/xe/xe_tile_types.h | 4 +-
5 files changed, 56 insertions(+), 11 deletions(-)
--
2.43.0
next reply other threads:[~2026-04-02 17:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 17:42 Raag Jadav [this message]
2026-04-02 17:42 ` [PATCH v2 1/4] drm/xe/hw_error: Setup hardware error routing Raag Jadav
2026-04-02 17:42 ` [PATCH v2 2/4] drm/xe/hw_error: Reuse CSC worker for generic error handling Raag Jadav
2026-04-02 17:42 ` [PATCH v2 3/4] drm/xe/hw_error: Allow debugging hardware errors Raag Jadav
2026-04-02 17:42 ` [PATCH v2 4/4] drm/xe/debugfs: Update hardware error routing with wedged.mode Raag Jadav
2026-04-02 17:53 ` ✓ CI.KUnit: success for Hardware Error handling for Crescent Island (rev2) Patchwork
2026-04-02 18:43 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-03 6:37 ` ✓ Xe.CI.FULL: " 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=20260402174229.1062874-1-raag.jadav@intel.com \
--to=raag.jadav@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=mallesh.koujalagi@intel.com \
--cc=matthew.brost@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=umesh.nerlige.ramappa@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