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, himal.prasad.ghimiray@intel.com,
arvind.yadav@intel.com, syed.abdul.muqthyar.ahmed@intel.com,
nitin.r.gote@intel.com, matthew.d.roper@intel.com
Subject: [PATCH v8 0/3] Extend CPER records with RAS info queue data
Date: Fri, 20 Nov 2026 10:03:03 +0530 [thread overview]
Message-ID: <20261120043303.107183-5-badal.nilawar@intel.com> (raw)
This series continues the RAS info queue support from
https://patchwork.freedesktop.org/series/169692/#rev5
v8:
- Address Raag's review comments on info queue draining and CPER
construction: naming, helper APIs, assertions, and formatting.
- Fix the single-chunk drain assertion and missing kernel-doc
reported by Sashiko.
Badal Nilawar (3):
drm/xe/cper: Drop redundant counter argument
drm/xe/xe_ras: Add support to retrieve info queue data
drm/xe/cper: Prepare Intel CPER info records
drivers/gpu/drm/xe/xe_cper.c | 263 +++++++++++++++++-
drivers/gpu/drm/xe/xe_cper.h | 3 -
drivers/gpu/drm/xe/xe_cper_types.h | 59 +++-
drivers/gpu/drm/xe/xe_ras.c | 189 ++++++++++++-
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 +
7 files changed, 620 insertions(+), 19 deletions(-)
--
2.56.0
next reply other threads:[~2026-11-20 4:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 4:33 Badal Nilawar [this message]
2026-11-20 4:33 ` [PATCH v8 1/3] drm/xe/cper: Drop redundant counter argument Badal Nilawar
2026-11-20 4:33 ` [PATCH v8 2/3] drm/xe/xe_ras: Add support to retrieve info queue data Badal Nilawar
2026-11-20 4:42 ` sashiko-bot
2026-11-20 4:33 ` [PATCH v8 3/3] drm/xe/cper: Prepare Intel CPER info records 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=20261120043303.107183-5-badal.nilawar@intel.com \
--to=badal.nilawar@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@intel.com \
--cc=arvind.yadav@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=matthew.d.roper@intel.com \
--cc=nitin.r.gote@intel.com \
--cc=raag.jadav@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