From: Aravind Iddamsetty <aravind.iddamsetty@linux.intel.com>
To: Riana Tauro <riana.tauro@intel.com>, intel-xe@lists.freedesktop.org
Cc: anshuman.gupta@intel.com, rodrigo.vivi@intel.com,
badal.nilawar@intel.com, raag.jadav@intel.com,
ravi.kishore.koppuravuri@intel.com, mallesh.koujalagi@intel.com
Subject: Re: [PATCH 2/5] drm/xe/uapi: Add additional error components to XE DRM RAS
Date: Wed, 25 Mar 2026 14:54:40 +0530 [thread overview]
Message-ID: <a9ced237-84b1-451d-ad11-bbf422282f06@linux.intel.com> (raw)
In-Reply-To: <20260320102607.1017511-3-riana.tauro@intel.com>
On 20-03-2026 15:55, Riana Tauro wrote:
> Add additional Error components supported by XE RAS (Reliability,
> Availability and Serviceability).
>
> Signed-off-by: Riana Tauro <riana.tauro@intel.com>
> ---
> include/uapi/drm/xe_drm.h | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h
> index f8b2afb20540..a1b1e15209cf 100644
> --- a/include/uapi/drm/xe_drm.h
> +++ b/include/uapi/drm/xe_drm.h
> @@ -2432,6 +2432,12 @@ enum drm_xe_ras_error_component {
> DRM_XE_RAS_ERR_COMP_CORE_COMPUTE = 1,
> /** @DRM_XE_RAS_ERR_COMP_SOC_INTERNAL: SoC Internal Error */
> DRM_XE_RAS_ERR_COMP_SOC_INTERNAL,
> + /** @DRM_XE_RAS_ERR_COMP_DEVICE_MEMORY: Device Memory Error */
> + DRM_XE_RAS_ERR_COMP_DEVICE_MEMORY,
> + /** @DRM_XE_RAS_ERR_COMP_PCIE: PCIe Subsystem Error */
> + DRM_XE_RAS_ERR_COMP_PCIE,
> + /** @DRM_XE_RAS_ERR_COMP_FABRIC: Fabric Subsystem Error */
> + DRM_XE_RAS_ERR_COMP_FABRIC,
> /** @DRM_XE_RAS_ERR_COMP_MAX: Max Error */
> DRM_XE_RAS_ERR_COMP_MAX /* non-ABI */
> };
> @@ -2449,7 +2455,10 @@ enum drm_xe_ras_error_component {
> */
> #define DRM_XE_RAS_ERROR_COMPONENT_NAMES { \
> [DRM_XE_RAS_ERR_COMP_CORE_COMPUTE] = "core-compute", \
> - [DRM_XE_RAS_ERR_COMP_SOC_INTERNAL] = "soc-internal" \
> + [DRM_XE_RAS_ERR_COMP_SOC_INTERNAL] = "soc-internal", \
> + [DRM_XE_RAS_ERR_COMP_DEVICE_MEMORY] = "device-memory", \
> + [DRM_XE_RAS_ERR_COMP_PCIE] = "pcie", \
> + [DRM_XE_RAS_ERR_COMP_FABRIC] = "fabric", \
> }
>
Reviewed-by: Aravind Iddamsetty <aravind.iddamsetty@linux.intel.com>
Thanks,
Aravind.
> #if defined(__cplusplus)
next prev parent reply other threads:[~2026-03-25 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 10:25 [PATCH 0/5] Add get-error-counter support for CRI Riana Tauro
2026-03-20 10:25 ` [PATCH 1/5] drm/xe/xe_sysctrl: Add System controller patch Riana Tauro
2026-03-20 10:25 ` [PATCH 2/5] drm/xe/uapi: Add additional error components to XE DRM RAS Riana Tauro
2026-03-25 9:24 ` Aravind Iddamsetty [this message]
2026-03-20 10:25 ` [PATCH 3/5] drm/xe/ras: Add flag for Xe RAS Riana Tauro
2026-03-20 10:25 ` [PATCH 4/5] drm/xe/xe_ras: Add structures and commands for get counter Riana Tauro
2026-03-20 10:26 ` [PATCH 5/5] drm/xe/xe_ras: Add support to query error counter for CRI Riana Tauro
2026-03-20 10:33 ` ✗ CI.checkpatch: warning for Add get-error-counter support " Patchwork
2026-03-20 10:35 ` ✓ CI.KUnit: success " Patchwork
2026-03-20 11:16 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-03-21 8:10 ` ✓ Xe.CI.FULL: success " 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=a9ced237-84b1-451d-ad11-bbf422282f06@linux.intel.com \
--to=aravind.iddamsetty@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=mallesh.koujalagi@intel.com \
--cc=raag.jadav@intel.com \
--cc=ravi.kishore.koppuravuri@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