From: Raag Jadav <raag.jadav@intel.com>
To: Riana Tauro <riana.tauro@intel.com>
Cc: intel-xe@lists.freedesktop.org, anshuman.gupta@intel.com,
rodrigo.vivi@intel.com, aravind.iddamsetty@linux.intel.com,
badal.nilawar@intel.com, ravi.kishore.koppuravuri@intel.com,
mallesh.koujalagi@intel.com, soham.purkait@intel.com
Subject: Re: [PATCH v3 06/10] drm/xe/xe_ras: Add structures and commands for Uncorrectable Core Compute Errors
Date: Tue, 7 Apr 2026 07:59:32 +0200 [thread overview]
Message-ID: <adSdRJc64v0ufcki@black.igk.intel.com> (raw)
In-Reply-To: <20260402070131.1603828-18-riana.tauro@intel.com>
On Thu, Apr 02, 2026 at 12:31:37PM +0530, Riana Tauro wrote:
> Add the sysctrl commands and response structures for Uncorrectable
> Core Compute errors.
...
> +static const char * const xe_ras_severities[] = {
> + [XE_RAS_SEVERITY_NOT_SUPPORTED] = "Not Supported",
> + [XE_RAS_SEVERITY_CORRECTABLE] = "Correctable",
> + [XE_RAS_SEVERITY_UNCORRECTABLE] = "Uncorrectable",
> + [XE_RAS_SEVERITY_INFORMATIONAL] = "Informational",
> +};
> +static_assert(ARRAY_SIZE(xe_ras_severities) == XE_RAS_SEVERITY_MAX);
> +
> +static const char * const xe_ras_components[] = {
> + [XE_RAS_COMPONENT_NOT_SUPPORTED] = "Not Supported",
> + [XE_RAS_COMPONENT_DEVICE_MEMORY] = "Device Memory",
> + [XE_RAS_COMPONENT_CORE_COMPUTE] = "Core Compute",
> + [XE_RAS_COMPONENT_RESERVED] = "Reserved",
> + [XE_RAS_COMPONENT_PCIE] = "PCIe",
> + [XE_RAS_COMPONENT_FABRIC] = "Fabric",
> + [XE_RAS_COMPONENT_SOC_INTERNAL] = "SoC Internal",
> +};
> +static_assert(ARRAY_SIZE(xe_ras_components) == XE_RAS_COMPONENT_MAX);
> +
> +static inline const char *severity_to_str(struct xe_device *xe, u32 severity)
> +{
> + xe_assert(xe, severity < XE_RAS_SEVERITY_MAX);
> +
> + return severity < XE_RAS_SEVERITY_MAX ? xe_ras_severities[severity] : "Unknown";
Rethinking about this, since we already have NOT_SUPPORTED member, can we
reuse it for "Unknown"?
static inline const char *sev_to_str(struct xe_device *xe, u32 sev)
{
if (sev >= XE_RAS_SEV_MAX)
sev = XE_RAS_SEV_NOT_SUPPORTED;
xe_assert(xe, severity != XE_RAS_SEV_NOT_SUPPORTED);
return xe_ras_severities[sev];
}
Or you can choose to drop xe_assert() entirely if it makes more sense.
> +}
> +
> +static inline const char *comp_to_str(struct xe_device *xe, u32 comp)
> +{
> + xe_assert(xe, comp < XE_RAS_COMPONENT_MAX);
> +
> + return comp < XE_RAS_COMPONENT_MAX ? xe_ras_components[comp] : "Unknown";
Ditto.
Raag
> +}
next prev parent reply other threads:[~2026-04-07 5:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 7:01 [PATCH v3 00/10] Introduce Xe Uncorrectable Error Handling Riana Tauro
2026-04-02 7:01 ` [PATCH v3 01/10] drm/xe/xe_survivability: Decouple survivability info from boot survivability Riana Tauro
2026-04-02 7:01 ` [PATCH v3 02/10] drm/xe/xe_pci_error: Implement PCI error recovery callbacks Riana Tauro
2026-04-07 4:50 ` Matthew Brost
2026-04-02 7:01 ` [PATCH v3 03/10] drm/xe/xe_pci_error: Group all devres to release them on PCIe slot reset Riana Tauro
2026-04-02 7:01 ` [PATCH v3 04/10] drm/xe: Skip device access during PCI error recovery Riana Tauro
2026-04-02 7:01 ` [PATCH v3 05/10] drm/xe/xe_ras: Initialize Uncorrectable AER Registers Riana Tauro
2026-04-07 5:50 ` Raag Jadav
2026-04-02 7:01 ` [PATCH v3 06/10] drm/xe/xe_ras: Add structures and commands for Uncorrectable Core Compute Errors Riana Tauro
2026-04-07 5:59 ` Raag Jadav [this message]
2026-04-02 7:01 ` [PATCH v3 07/10] drm/xe/xe_ras: Add support for Uncorrectable Core-Compute errors Riana Tauro
2026-04-08 11:15 ` Raag Jadav
2026-04-02 7:01 ` [PATCH v3 08/10] drm/xe/xe_ras: Add structures for SoC Internal errors Riana Tauro
2026-04-08 11:18 ` Raag Jadav
2026-04-02 7:01 ` [PATCH v3 09/10] drm/xe/xe_ras: Handle Uncorrectable " Riana Tauro
2026-04-02 7:01 ` [PATCH v3 10/10] drm/xe/xe_pci_error: Process errors in mmio_enabled Riana Tauro
2026-04-02 8:01 ` ✗ CI.checkpatch: warning for Introduce Xe Uncorrectable Error Handling (rev3) Patchwork
2026-04-02 8:02 ` ✓ CI.KUnit: success " Patchwork
2026-04-02 8:50 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-02 15:08 ` ✓ 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=adSdRJc64v0ufcki@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=anshuman.gupta@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=ravi.kishore.koppuravuri@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=soham.purkait@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