From: "Mallesh, Koujalagi" <mallesh.koujalagi@intel.com>
To: "Tauro, Riana" <riana.tauro@intel.com>,
<intel-xe@lists.freedesktop.org>, <rodrigo.vivi@intel.com>,
<matthew.brost@intel.com>, <thomas.hellstrom@linux.intel.com>
Cc: <anshuman.gupta@intel.com>, <badal.nilawar@intel.com>,
<vinay.belgaumkar@intel.com>, <aravind.iddamsetty@intel.com>,
<karthik.poosa@intel.com>, <sk.anirban@intel.com>,
<raag.jadav@intel.com>
Subject: Re: [RFC PATCH v3 1/3] drm/xe: Add error Signature IDs for RAS logging
Date: Tue, 23 Jun 2026 13:11:02 +0530 [thread overview]
Message-ID: <3188fbea-985b-4336-8503-4b235f33beab@intel.com> (raw)
In-Reply-To: <2c2b5167-97fd-49fb-88f4-71e1dd1b3122@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2806 bytes --]
On 19-06-2026 11:18 am, Tauro, Riana wrote:
>
> On 17-06-2026 16:17, Mallesh Koujalagi wrote:
>> Every GPU fault needs a stable numeric label so monitoring tools can
>
> GPU fault does not need a label. This patch introduces so it's easy
> for tools /script to monitor.
>
You are right. I will update this in the next revision.
>> identify what went wrong without parsing log text. Add xe_sig_ids.h
>> which defines those labels, called SIG_IDs.
>>
>> Signed-off-by: Mallesh Koujalagi <mallesh.koujalagi@intel.com>
>> ---
>> v3:
>> - Add HW SIG IDS details. (Riana)
>> ---
>> drivers/gpu/drm/xe/xe_sig_ids.h | 29 +++++++++++++++++++++++++++++
>> 1 file changed, 29 insertions(+)
>> create mode 100644 drivers/gpu/drm/xe/xe_sig_ids.h
>>
>> diff --git a/drivers/gpu/drm/xe/xe_sig_ids.h
>> b/drivers/gpu/drm/xe/xe_sig_ids.h
>> new file mode 100644
>> index 000000000000..7badd0d7ad72
>> --- /dev/null
>> +++ b/drivers/gpu/drm/xe/xe_sig_ids.h
>> @@ -0,0 +1,29 @@
>> +/* SPDX-License-Identifier: MIT */
>> +/*
>> + * Copyright © 2026 Intel Corporation
>> + */
>> +
>> +#ifndef _XE_SIG_IDS_H_
>> +#define _XE_SIG_IDS_H_
>
> Document would be more relevant here
>
Ack, I'll move here.
>> +
>> +/*
>> + * Driver SIG_IDs
>> + */
>> +#define XE_SIG_PROBE 1 /* FATAL: probe failed */
>> +#define XE_SIG_WEDGED 2 /* FATAL: device wedged */
>> +#define XE_SIG_SURVIVABILITY 3 /* FATAL: survivability mode */
>> +#define XE_SIG_FW 4 /* RECOVERABLE:
>> GuC/HuC/UC/GSC/CSC/PCODE */
>> +#define XE_SIG_GT_TDR 5 /* RECOVERABLE: engine hang /
>> reset */
>> +#define XE_SIG_MEM_FAULT 6 /* RECOVERABLE: VM bind, page
>> fault, GTT */
>> +#define XE_SIG_IO_BUS 7 /* RECOVERABLE: runtime
>> PCIe/IOMMU/MMIO */
>> +
>> +/*
>> + * HW SIG_IDs
>
> Acronym needed? Mention Hardware error
>
Good point. I will update the comment to explicitly mention “Hardware
errors” in the next revision.
>> + */
>> +#define XE_SIG_HW_DEVICE_MEMORY 8 /* Device memory errors
>> (e.g. ECC) */
>
> example not needed. If required please define
>
Agreed. I will drop the example and keep the comment concise
>> +#define XE_SIG_HW_CORE_COMPUTE 9 /* Compute/shader core
>> errors */
>> +#define XE_SIG_HW_PCIE 10 /* PCIe interface errors */
>> +#define XE_SIG_HW_FABRIC 11 /* On-package fabric errors */
> on-package?
It refers to the high speed interconnect between dies/tiles within the
same GPU.
I'll make the comment clearer in next revision.
Thanks,
-/Mallesh
>
> Thanks
> Riana
>
>
>> +#define XE_SIG_HW_SOC_INTERNAL 12 /* SoC-internal errors */
>> +
>> +#endif /* _XE_SIG_IDS_H_ */
[-- Attachment #2: Type: text/html, Size: 5983 bytes --]
next prev parent reply other threads:[~2026-06-23 7:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 10:47 [RFC PATCH v3 0/3] drm/xe: Structured RAS error logging infrastructure Mallesh Koujalagi
2026-06-17 10:47 ` [RFC PATCH v3 1/3] drm/xe: Add error Signature IDs for RAS logging Mallesh Koujalagi
2026-06-19 5:48 ` Tauro, Riana
2026-06-23 7:41 ` Mallesh, Koujalagi [this message]
2026-06-20 17:02 ` Michal Wajdeczko
2026-06-24 11:51 ` Mallesh, Koujalagi
2026-06-17 10:47 ` [RFC PATCH v3 2/3] drm/xe: Add RAS logging helpers Mallesh Koujalagi
2026-06-19 5:43 ` Tauro, Riana
2026-06-23 10:41 ` Mallesh, Koujalagi
2026-06-20 19:29 ` Michal Wajdeczko
2026-06-24 16:03 ` Mallesh, Koujalagi
2026-07-03 11:23 ` Tauro, Riana
2026-06-17 10:47 ` [RFC PATCH v3 3/3] drm/xe: use XE_RAS_WEDGED macro in xe_device_declare_wedged Mallesh Koujalagi
2026-06-17 16:06 ` Bhadane, Dnyaneshwar
2026-06-20 19:39 ` Michal Wajdeczko
2026-06-24 16:16 ` Mallesh, Koujalagi
2026-06-17 11:11 ` ✗ CI.checkpatch: warning for drm/xe: Structured RAS error logging infrastructure (rev3) Patchwork
2026-06-17 11:11 ` ✗ CI.KUnit: failure " 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=3188fbea-985b-4336-8503-4b235f33beab@intel.com \
--to=mallesh.koujalagi@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=karthik.poosa@intel.com \
--cc=matthew.brost@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=sk.anirban@intel.com \
--cc=thomas.hellstrom@linux.intel.com \
--cc=vinay.belgaumkar@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