From: Raag Jadav <raag.jadav@intel.com>
To: Badal Nilawar <badal.nilawar@intel.com>
Cc: intel-xe@lists.freedesktop.org, anshuman.gupta@intel.com,
rodrigo.vivi@intel.com, daniele.ceraolospurio@intel.com,
riana.tauro@intel.com, mallesh.koujalagi@intel.com,
aravind.iddamsetty@intel.com, himal.prasad.ghimiray@intel.com,
arvind.yadav@intel.com, syed.abdul.muqthyar.ahmed@intel.com,
nitin.r.gote@intel.com, pravalika.gurram@intel.com
Subject: Re: [PATCH v4 00/12] Add CPER logging support for CRI
Date: Mon, 12 Oct 2026 08:14:59 +0200 [thread overview]
Message-ID: <asx642wl72PkTZY4@black.igk.intel.com> (raw)
In-Reply-To: <20261009104602.1075405-14-badal.nilawar@intel.com>
On Fri, Oct 09, 2026 at 04:16:03PM +0530, Badal Nilawar wrote:
> This patch series adds CPER (Common Platform Error Record) logging support
> for Correctable errors reported by Intel Xe GPUs. CPER logging is done
Is it still correctable errors?
Raag
> through trace event.
>
> v2:
> - Extended CPER logging to Uncorrectable errors and xe_ras_get_counter
> request
> - Log CPER records via xe_log SIGID infra
>
> v3:
> - Added the patches in incremental order (Raag)
> - Fixed Sashiko warnings which are applicable
>
> v4:
> - Split the patches further for incremental review (Raag)
> - Refactor info queue handling (Raag)
> - Fix applicable Sashiko warnings
>
> Badal Nilawar (12):
> drm/xe/cper: Add CPER reporting entry point for xe_log
> drm/xe/cper: Retrieve the error counter record for CPER reporting
> drm/xe/cper: Initialize Intel-specific error section header
> drm/xe/cper: Construct CPER record for hardware errors
> drm/xe/xe_ras: Add support to retrieve info queue data for CRI
> drm/xe/cper: Prepare Intel CPER error info records
> drm/xe/cper: Log CPER records for aggregate counter retrieval
> drm/xe/cper: Emit cper record to trace buf
> drm/xe/xe_ras: Report device memory errors using SIGID
> drm/xe/xe_ras: Report core compute errors using SIGID
> drm/xe/xe_ras: Report soc internal errors using SIGID
> drm/xe/xe_ras: Report correctable errors using SIGID
>
> .../ABI/testing/sysfs-driver-intel-xe-cper | 18 +
> drivers/gpu/drm/xe/Makefile | 3 +
> drivers/gpu/drm/xe/xe_cper.c | 530 ++++++++++++++++++
> drivers/gpu/drm/xe/xe_cper.h | 37 ++
> drivers/gpu/drm/xe/xe_cper_types.h | 185 ++++++
> drivers/gpu/drm/xe/xe_device_types.h | 4 +
> drivers/gpu/drm/xe/xe_log.c | 5 +-
> drivers/gpu/drm/xe/xe_ras.c | 254 ++++++++-
> drivers/gpu/drm/xe/xe_ras.h | 5 +
> drivers/gpu/drm/xe/xe_ras_types.h | 118 +++-
> drivers/gpu/drm/xe/xe_sysctrl_mailbox_types.h | 2 +
> drivers/gpu/drm/xe/xe_trace_cper.c | 9 +
> drivers/gpu/drm/xe/xe_trace_cper.h | 66 +++
> 13 files changed, 1202 insertions(+), 34 deletions(-)
> create mode 100644 Documentation/ABI/testing/sysfs-driver-intel-xe-cper
> create mode 100644 drivers/gpu/drm/xe/xe_cper.c
> create mode 100644 drivers/gpu/drm/xe/xe_cper.h
> create mode 100644 drivers/gpu/drm/xe/xe_cper_types.h
> create mode 100644 drivers/gpu/drm/xe/xe_trace_cper.c
> create mode 100644 drivers/gpu/drm/xe/xe_trace_cper.h
>
> --
> 2.54.0
>
prev parent reply other threads:[~2026-10-12 6:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 10:46 [PATCH v4 00/12] Add CPER logging support for CRI Badal Nilawar
2026-10-09 10:46 ` [PATCH v4 01/12] drm/xe/cper: Add CPER reporting entry point for xe_log Badal Nilawar
2026-10-09 10:43 ` sashiko-bot
2026-10-09 12:17 ` Nilawar, Badal
2026-10-12 6:18 ` Raag Jadav
2026-10-09 10:46 ` [PATCH v4 02/12] drm/xe/cper: Retrieve the error counter record for CPER reporting Badal Nilawar
2026-10-09 10:46 ` sashiko-bot
2026-10-09 12:27 ` Nilawar, Badal
2026-10-12 9:07 ` Raag Jadav
2026-10-09 10:46 ` [PATCH v4 03/12] drm/xe/cper: Initialize Intel-specific error section header Badal Nilawar
2026-10-09 10:46 ` [PATCH v4 04/12] drm/xe/cper: Construct CPER record for hardware errors Badal Nilawar
2026-10-09 10:46 ` [PATCH v4 05/12] drm/xe/xe_ras: Add support to retrieve info queue data for CRI Badal Nilawar
2026-10-09 10:40 ` sashiko-bot
2026-10-09 12:45 ` Nilawar, Badal
2026-10-09 10:46 ` [PATCH v4 06/12] drm/xe/cper: Prepare Intel CPER error info records Badal Nilawar
2026-10-09 10:41 ` sashiko-bot
2026-10-09 13:07 ` Nilawar, Badal
2026-10-09 10:46 ` [PATCH v4 07/12] drm/xe/cper: Log CPER records for aggregate counter retrieval Badal Nilawar
2026-10-09 10:46 ` [PATCH v4 08/12] drm/xe/cper: Emit cper record to trace buf Badal Nilawar
2026-10-09 10:38 ` sashiko-bot
2026-10-09 10:46 ` [PATCH v4 09/12] drm/xe/xe_ras: Report device memory errors using SIGID Badal Nilawar
2026-10-09 10:46 ` [PATCH v4 10/12] drm/xe/xe_ras: Report core compute " Badal Nilawar
2026-10-09 10:46 ` [PATCH v4 11/12] drm/xe/xe_ras: Report soc internal " Badal Nilawar
2026-10-09 10:46 ` [PATCH v4 12/12] drm/xe/xe_ras: Report correctable " Badal Nilawar
2026-10-09 10:50 ` sashiko-bot
2026-10-09 10:54 ` ✗ CI.checkpatch: warning for Add CPER logging support for CRI (rev4) Patchwork
2026-10-09 10:56 ` ✓ CI.KUnit: success " Patchwork
2026-10-09 12:03 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-10-09 15:13 ` ✓ Xe.CI.FULL: success " Patchwork
2026-10-12 6:14 ` Raag Jadav [this message]
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=asx642wl72PkTZY4@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@intel.com \
--cc=arvind.yadav@intel.com \
--cc=badal.nilawar@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=mallesh.koujalagi@intel.com \
--cc=nitin.r.gote@intel.com \
--cc=pravalika.gurram@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=syed.abdul.muqthyar.ahmed@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