From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: intel-xe@lists.freedesktop.org, rodrigo.vivi@intel.com,
badal.nilawar@intel.com, riana.tauro@intel.com,
michal.wajdeczko@intel.com, aravind.iddamsetty@linux.intel.com,
mallesh.koujalagi@intel.com
Subject: [PATCH 0/4] Use SIGID API for PCODE and CSC
Date: Tue, 11 Aug 2026 16:52:55 -0700 [thread overview]
Message-ID: <20260811235254.153783-6-umesh.nerlige.ramappa@intel.com> (raw)
For PCODE and CSC, this series uses xe_log SIGID API introduced in:
https://patchwork.freedesktop.org/series/171022/
Note that PCODE changes are partially present in the below series and
may be picked up by their future revisions.
https://patchwork.freedesktop.org/series/171725/
https://patchwork.freedesktop.org/series/171022/
The purpose of this series is to ensure all relevant logs are reported
for CSC and PCODE.
Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Mallesh Koujalagi (1):
drm/xe/log: DO NOT REVIEW
Umesh Nerlige Ramappa (3):
drm/xe/pcode: Use int instead of u32 for mailbox status
drm/xe/pcode: Report pcode errors using SIGID
drm/xe/ras: Report CSC errors using SIGID
Documentation/gpu/xe/index.rst | 1 +
Documentation/gpu/xe/xe_sigid.rst | 14 ++
drivers/gpu/drm/xe/Makefile | 1 +
drivers/gpu/drm/xe/abi/xe_log_abi.h | 198 +++++++++++++++++++++++
drivers/gpu/drm/xe/abi/xe_sigid_abi.h | 195 +++++++++++++++++++++++
drivers/gpu/drm/xe/xe_any.h | 142 +++++++++++++++++
drivers/gpu/drm/xe/xe_log.c | 221 ++++++++++++++++++++++++++
drivers/gpu/drm/xe/xe_log.h | 158 ++++++++++++++++++
drivers/gpu/drm/xe/xe_pcode.c | 17 +-
drivers/gpu/drm/xe/xe_ras.c | 16 +-
10 files changed, 952 insertions(+), 11 deletions(-)
create mode 100644 Documentation/gpu/xe/xe_sigid.rst
create mode 100644 drivers/gpu/drm/xe/abi/xe_log_abi.h
create mode 100644 drivers/gpu/drm/xe/abi/xe_sigid_abi.h
create mode 100644 drivers/gpu/drm/xe/xe_any.h
create mode 100644 drivers/gpu/drm/xe/xe_log.c
create mode 100644 drivers/gpu/drm/xe/xe_log.h
--
2.51.0
next reply other threads:[~2026-08-11 23:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 23:52 Umesh Nerlige Ramappa [this message]
2026-08-11 23:52 ` [PATCH 1/4] drm/xe/log: DO NOT REVIEW Umesh Nerlige Ramappa
2026-08-11 23:52 ` [PATCH 2/4] drm/xe/pcode: Use int instead of u32 for mailbox status Umesh Nerlige Ramappa
2026-08-12 0:04 ` sashiko-bot
2026-08-11 23:52 ` [PATCH 3/4] drm/xe/pcode: Report pcode errors using SIGID Umesh Nerlige Ramappa
2026-08-12 0:01 ` sashiko-bot
2026-08-12 13:35 ` Nilawar, Badal
2026-08-12 18:07 ` Umesh Nerlige Ramappa
2026-08-12 19:45 ` Michal Wajdeczko
2026-08-13 16:53 ` Umesh Nerlige Ramappa
2026-08-11 23:52 ` [PATCH 4/4] drm/xe/ras: Report CSC " Umesh Nerlige Ramappa
2026-08-12 19:52 ` Michal Wajdeczko
2026-08-14 18:27 ` Umesh Nerlige Ramappa
2026-08-15 7:59 ` Michal Wajdeczko
2026-08-18 22:52 ` Umesh Nerlige Ramappa
2026-08-11 23:59 ` ✗ CI.checkpatch: warning for Use SIGID API for PCODE and CSC Patchwork
2026-08-12 0:00 ` ✓ CI.KUnit: success " Patchwork
2026-08-12 0:38 ` ✓ Xe.CI.BAT: " Patchwork
2026-08-12 1:48 ` ✓ 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=20260811235254.153783-6-umesh.nerlige.ramappa@intel.com \
--to=umesh.nerlige.ramappa@intel.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=mallesh.koujalagi@intel.com \
--cc=michal.wajdeczko@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