From: Riana Tauro <riana.tauro@intel.com>
To: "Mallesh, Koujalagi" <mallesh.koujalagi@intel.com>,
<intel-xe@lists.freedesktop.org>
Cc: <anshuman.gupta@intel.com>, <rodrigo.vivi@intel.com>,
<aravind.iddamsetty@linux.intel.com>, <badal.nilawar@intel.com>,
<raag.jadav@intel.com>, <ravi.kishore.koppuravuri@intel.com>
Subject: Re: [PATCH 7/8] drm/xe/xe_ras: Add support for Uncorrectable Core-Compute errors
Date: Mon, 2 Feb 2026 14:08:17 +0530 [thread overview]
Message-ID: <052efa8b-665b-454f-9329-74df8b534ca9@intel.com> (raw)
In-Reply-To: <b9c82350-c32f-4cd3-9d69-c9c7aa1a347a@intel.com>
On 1/27/2026 5:14 PM, Mallesh, Koujalagi wrote:
> Hi Riana,
>
> On 22-01-2026 03:36 pm, Riana Tauro wrote:
>> Uncorrectable Core-Compute errors are classified into Global and Local
>> errors.
>>
>> Global error is an error that affects the entire device requiring a
>> reset. This type of error is not isolated. When an AER is reported and
>> error_detected is invoked return PCI_ERS_RESULT_NEED_RESET.
>>
>> A Local error is confined to a specific component or context like a
>> engine. These errors can be contained and recovered by resetting
>> only the affected part without distrupting the rest of the device.
>>
>> Upon detection of an Uncorrectable Local Core-Compute error, an AER is
>> generated and GuC is notified of the error. The KMD then sets
>> the context as non-runnable and initiates an engine reset.
>> (TODO: GuC <->KMD communication for the error).
>> Since the error is contained and recovered, PCI error handling
>> callback returns PCI_ERS_RESULT_RECOVERED.
>>
>> Signed-off-by: Riana Tauro<riana.tauro@intel.com>
>> ---
>> drivers/gpu/drm/xe/xe_ras.c | 109 +++++++++++++++++++++++++++++++++++-
>> drivers/gpu/drm/xe/xe_ras.h | 3 +
>> 2 files changed, 110 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_ras.c b/drivers/gpu/drm/xe/xe_ras.c
>> index ace08d8d8d46..2a98cb116dc7 100644
>> --- a/drivers/gpu/drm/xe/xe_ras.c
>> +++ b/drivers/gpu/drm/xe/xe_ras.c
>> @@ -2,11 +2,16 @@
>> /*
>> * Copyright © 2026 Intel Corporation
>> */
>> -#include <linux/pci.h>
>> -
>> #include "xe_assert.h"
>> #include "xe_device_types.h"
>> +#include "xe_printk.h"
>> #include "xe_ras.h"
>> +#include "xe_ras_types.h"
>> +#include "xe_sysctrl_mailbox.h"
>> +#include "xe_sysctrl_mailbox_types.h"
>> +
>> +#define COMPUTE_ERROR_SEVERITY_MASK GENMASK(26, 25)
>> +#define GLOBAL_UNCORR_ERROR 2
>> /* Severity classification of detected errors */
>> enum xe_ras_severity {
>> @@ -60,6 +65,106 @@ static inline const char *comp_to_str(struct
>> xe_device *xe, u32 comp)
>> return xe_ras_components[comp];
>> }
>> +static void log_ras_error(struct xe_device *xe, struct
>> xe_ras_error_class *error_class)
>> +{
>> + struct xe_ras_error_common common_info = error_class->common;
>> + struct xe_ras_error_product product_info = error_class->product;
>> + u8 tile = product_info.unit.tile;
>> + u32 instance = product_info.unit.instance;
>> + u32 cause = product_info.error_cause.cause;
>> +
>> + xe_err(xe, "[RAS]: Tile%u, Instance %u, %s %s Error detected
>> Cause: 0x%x",
>> + tile, instance, severity_to_str(xe, common_info.severity),
>> + comp_to_str(xe, common_info.component), cause);
>> +}
>> +
>> +static pci_ers_result_t handle_compute_errors(struct xe_device *xe,
>> struct xe_ras_error_array *arr)
>> +{
>> + struct xe_ras_compute_error *error_info = (struct
>> xe_ras_compute_error *)arr->error_details;
>> + u8 uncorr_type;
>> +
>> + uncorr_type = FIELD_GET(COMPUTE_ERROR_SEVERITY_MASK, error_info-
>> >error_log_header);
>> + log_ras_error(xe, &arr->error_class);
>> +
>> + xe_err(xe, "[RAS]: Core Compute Error: timestamp %llu Uncorrected
>> error type %u\n",
>> + arr->timestamp, uncorr_type);
>> +
>> + /* Request a RESET if error is global */
>> + if (uncorr_type == GLOBAL_UNCORR_ERROR)
>> + return PCI_ERS_RESULT_NEED_RESET;
>> +
>> + /* Local errors are recovered using a engine reset */
>> + return PCI_ERS_RESULT_RECOVERED;
>> +}
>> +
>> +/**
>> + * xe_ras_process_errors - Process and contain hardware errors
>> + * @xe: xe device instance
>> + *
>> + * Get error details from system controller and return recovery
>> + * method. Called only from PCI error handling.
>> + *
>> + * Returns: PCI_ERS_RESULT_RECOVERED if recovered or if no recovery
>> needed,
>> + * PCI_ERS_RESULT_NEED_RESET otherwise.
>> + */
>> +pci_ers_result_t xe_ras_process_errors(struct xe_device *xe)
>> +{
>> + struct xe_sysctrl_mailbox_command command = {0};
>> + struct xe_sysctrl_mailbox_app_msg_hdr msg_hdr = {0};
>> + struct xe_ras_get_error_response response;
>> + u32 req_hdr;
>> + size_t rlen;
>> + int ret;
>> +
>> + if (!xe->info.has_sysctrl)
>> + return PCI_ERS_RESULT_NEED_RESET;
>> +
>> + req_hdr = FIELD_PREP(APP_HDR_GROUP_ID_MASK, XE_SYSCTRL_GROUP_GFSP) |
>> + FIELD_PREP(APP_HDR_COMMAND_MASK,
>> XE_SYSCTRL_CMD_GET_SOC_ERROR);
>> +
>> + msg_hdr.data = req_hdr;
>> + command.header = msg_hdr;
>> + command.data_out = &response;
>> + command.data_out_len = sizeof(response);
>> +
>> + do {
>> + memset(&response, 0, sizeof(response));
>> + rlen = 0;
>> +
>> + ret = xe_sysctrl_send_command(xe, &command, &rlen);
>> + if (ret || !rlen) {
>> + xe_err(xe, "[RAS]: Sysctrl error ret %d\n", ret);
>> + goto err;
>> + }
>> +
>> + if (rlen != sizeof(response)) {
>> + xe_err(xe, "[RAS]: Sysctrl response does not match len!!
>> \n");
>> + goto err;
>> + }
>> +
>
> Array bound check is required for response.num_errors. if num_errors
> are more than 3 then potentials security issue (accessing uninitialized
> or arbitrary memory).
yeah agree. Will fix this in next revision
Thanks
Riana
>
> Thanks,
>
> -/Mallesh
>
>> + for (int i = 0; i < response.num_errors; i++) {
>> + struct xe_ras_error_array arr = response.error_arr[i];
>> + struct xe_ras_error_class error_class;
>> + u8 component;
>> +
>> + error_class = arr.error_class;
>> + component = error_class.common.component;
>> +
>> + if (component == XE_RAS_COMPONENT_CORE_COMPUTE) {
>> + ret = handle_compute_errors(xe, &arr);
>> + if (ret == PCI_ERS_RESULT_NEED_RESET)
>> + goto err;
>> + }
>> + }
>> +
>> + } while (response.additional_errors);
>> +
>> + return PCI_ERS_RESULT_RECOVERED;
>> +
>> +err:
>> + return PCI_ERS_RESULT_NEED_RESET;
>> +}
>> +
>> #ifdef CONFIG_PCIEAER
>> static void unmask_and_downgrade_internal_error(struct xe_device *xe)
>> {
>> diff --git a/drivers/gpu/drm/xe/xe_ras.h b/drivers/gpu/drm/xe/xe_ras.h
>> index 14cb973603e7..28400613c9a9 100644
>> --- a/drivers/gpu/drm/xe/xe_ras.h
>> +++ b/drivers/gpu/drm/xe/xe_ras.h
>> @@ -6,8 +6,11 @@
>> #ifndef _XE_RAS_H_
>> #define _XE_RAS_H_
>> +#include <linux/pci.h>
>> +
>> struct xe_device;
>> void xe_ras_init(struct xe_device *xe);
>> +pci_ers_result_t xe_ras_process_errors(struct xe_device *xe);
>> #endif
next prev parent reply other threads:[~2026-02-02 8:38 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 10:06 [PATCH 0/8] Introduce Xe Uncorrectable Error Handling Riana Tauro
2026-01-22 9:42 ` ✗ CI.checkpatch: warning for " Patchwork
2026-01-22 9:43 ` ✓ CI.KUnit: success " Patchwork
2026-01-22 10:06 ` [PATCH 1/8] drm/xe/xe_sysctrl: Add System controller patch Riana Tauro
2026-01-22 10:06 ` [PATCH 2/8] drm/xe/xe_pci_error: Implement PCI error recovery callbacks Riana Tauro
2026-01-27 22:49 ` Michal Wajdeczko
2026-02-02 9:45 ` Riana Tauro
2026-01-29 9:09 ` Nilawar, Badal
2026-02-02 13:19 ` Nilawar, Badal
2026-02-03 3:46 ` Riana Tauro
2026-02-03 3:41 ` Riana Tauro
2026-02-08 8:02 ` Raag Jadav
2026-02-24 3:23 ` Riana Tauro
2026-02-24 5:33 ` Raag Jadav
2026-02-16 8:53 ` Mallesh, Koujalagi
2026-02-24 3:26 ` Riana Tauro
2026-01-22 10:06 ` [PATCH 3/8] drm/xe/xe_pci_error: Group all devres to release them on PCIe slot reset Riana Tauro
2026-01-27 11:23 ` Mallesh, Koujalagi
2026-02-02 8:46 ` Riana Tauro
2026-01-22 10:06 ` [PATCH 4/8] drm/xe: Skip device access during PCI error recovery Riana Tauro
2026-01-22 10:06 ` [PATCH 5/8] drm/xe/xe_ras: Initialize Uncorrectable AER Registers Riana Tauro
2026-01-27 12:41 ` Mallesh, Koujalagi
2026-02-02 9:34 ` Riana Tauro
2026-02-04 8:38 ` Aravind Iddamsetty
2026-02-16 12:27 ` Mallesh, Koujalagi
2026-02-18 14:48 ` Riana Tauro
2026-01-22 10:06 ` [PATCH 6/8] drm/xe/xe_ras: Add structures and commands for Uncorrectable Core Compute Errors Riana Tauro
2026-02-23 14:19 ` Mallesh, Koujalagi
2026-02-23 14:30 ` Riana Tauro
2026-01-22 10:06 ` [PATCH 7/8] drm/xe/xe_ras: Add support for Uncorrectable Core-Compute errors Riana Tauro
2026-01-27 11:44 ` Mallesh, Koujalagi
2026-02-02 8:38 ` Riana Tauro [this message]
2026-01-27 14:03 ` Mallesh, Koujalagi
2026-02-02 8:54 ` Riana Tauro
2026-02-24 12:17 ` Mallesh, Koujalagi
2026-02-17 14:02 ` Raag Jadav
2026-02-23 14:10 ` Riana Tauro
2026-01-22 10:06 ` [PATCH 8/8] drm/xe/xe_pci_error: Process errors in mmio_enabled Riana Tauro
2026-02-24 12:46 ` Mallesh, Koujalagi
2026-01-22 10:21 ` ✓ Xe.CI.BAT: success for Introduce Xe Uncorrectable Error Handling Patchwork
2026-01-22 20:28 ` ✗ Xe.CI.Full: 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=052efa8b-665b-454f-9329-74df8b534ca9@intel.com \
--to=riana.tauro@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=raag.jadav@intel.com \
--cc=ravi.kishore.koppuravuri@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