From: Badal Nilawar <badal.nilawar@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: anshuman.gupta@intel.com, rodrigo.vivi@intel.com,
daniele.ceraolospurio@intel.com, raag.jadav@intel.com,
riana.tauro@intel.com, mallesh.koujalagi@intel.com,
aravind.iddamsetty@intel.com
Subject: [RFC PATCH 0/7] Add CPER logging support for CRI
Date: Thu, 2 Jul 2026 16:44:02 +0530 [thread overview]
Message-ID: <20260702111401.3680214-9-badal.nilawar@intel.com> (raw)
This patch series adds CPER (Common Platform Error Record) logging support
for Correctable errors reported by Intel Xe GPUs. CPER logging is done
through trace event.
In subsequent patches will add CPER logging support for Un-correctable errors.
Do not review patch "drm/xe: Add error Signature IDs for RAS logging" as
it is part of https://patchwork.freedesktop.org/series/168333/
Badal Nilawar (6):
drm/xe/xe_ras: Add support to retrieve info queue data for CRI
drm/xe/xe_ras: Refactor get_counter() to return response structure
drm/xe/cper: Add CPER structures and trace event
drm/xe/cper: APIs to prepare and log CPER record
drm/xe/cper: Prepare Intel CPER error info from info queue
drm/xe/cper: Log CPER record for correctable errors
Mallesh Koujalagi (1):
drm/xe: Add error Signature IDs for RAS logging
drivers/gpu/drm/xe/Makefile | 2 +
drivers/gpu/drm/xe/xe_cper.c | 215 ++++++++++++++
drivers/gpu/drm/xe/xe_cper.h | 30 ++
drivers/gpu/drm/xe/xe_cper_types.h | 186 ++++++++++++
drivers/gpu/drm/xe/xe_ras.c | 272 +++++++++++++++++-
drivers/gpu/drm/xe/xe_ras_types.h | 122 +++++++-
drivers/gpu/drm/xe/xe_sig_ids.h | 29 ++
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 | 65 +++++
10 files changed, 921 insertions(+), 11 deletions(-)
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_sig_ids.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
next reply other threads:[~2026-07-02 11:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 11:14 Badal Nilawar [this message]
2026-07-02 11:14 ` [RFC PATCH 1/7] drm/xe: Add error Signature IDs for RAS logging Badal Nilawar
2026-07-02 11:14 ` [RFC PATCH 2/7] drm/xe/xe_ras: Add support to retrieve info queue data for CRI Badal Nilawar
2026-07-07 12:29 ` Mallesh, Koujalagi
2026-07-02 11:14 ` [RFC PATCH 3/7] drm/xe/xe_ras: Refactor get_counter() to return response structure Badal Nilawar
2026-07-03 7:41 ` Tauro, Riana
2026-07-07 12:53 ` Mallesh, Koujalagi
2026-07-02 11:14 ` [RFC PATCH 4/7] drm/xe/cper: Add CPER structures and trace event Badal Nilawar
2026-07-02 11:14 ` [RFC PATCH 5/7] drm/xe/cper: APIs to prepare and log CPER record Badal Nilawar
2026-07-02 11:14 ` [RFC PATCH 6/7] drm/xe/cper: Prepare Intel CPER error info from info queue Badal Nilawar
2026-07-02 11:14 ` [RFC PATCH 7/7] drm/xe/cper: Log CPER record for correctable errors Badal Nilawar
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=20260702111401.3680214-9-badal.nilawar@intel.com \
--to=badal.nilawar@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=mallesh.koujalagi@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@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