From: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
To: Aravind Iddamsetty <aravind.iddamsetty@linux.intel.com>,
<intel-xe@lists.freedesktop.org>
Cc: Jani Nikula <jani.nikula@intel.com>,
Matt Roper <matthew.d.roper@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-xe] [PATCH v5 2/4] drm/xe: Log and count the GT hardware errors.
Date: Tue, 26 Sep 2023 10:38:36 +0530 [thread overview]
Message-ID: <ed406599-055d-4189-85e4-6232f5e8d127@intel.com> (raw)
In-Reply-To: <e6c3dae0-0713-db9e-93ef-cffc24b3b8a3@linux.intel.com>
On 26-09-2023 09:50, Aravind Iddamsetty wrote:
> On 23/08/23 14:28, Himal Prasad Ghimiray wrote:
>> For the errors reported by GT unit, read the GT error register.
>> Log and count these errors and clear the error register.
>>
>> Bspec: 53088, 53089, 53090
>>
>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> Cc: Aravind Iddamsetty <aravind.iddamsetty@intel.com>
>> Cc: Matthew Brost <matthew.brost@intel.com>
>> Cc: Matt Roper <matthew.d.roper@intel.com>
>> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>> Cc: Jani Nikula <jani.nikula@intel.com>
>> Signed-off-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
>> ---
>> drivers/gpu/drm/xe/regs/xe_gt_error_regs.h | 13 +++
>> drivers/gpu/drm/xe/xe_device_types.h | 1 +
>> drivers/gpu/drm/xe/xe_gt_types.h | 7 ++
>> drivers/gpu/drm/xe/xe_hw_error.c | 96 +++++++++++++++++++++-
>> drivers/gpu/drm/xe/xe_hw_error.h | 24 ++++++
>> 5 files changed, 140 insertions(+), 1 deletion(-)
>> create mode 100644 drivers/gpu/drm/xe/regs/xe_gt_error_regs.h
>>
>> diff --git a/drivers/gpu/drm/xe/regs/xe_gt_error_regs.h b/drivers/gpu/drm/xe/regs/xe_gt_error_regs.h
>> new file mode 100644
>> index 000000000000..6180704a6149
>> --- /dev/null
>> +++ b/drivers/gpu/drm/xe/regs/xe_gt_error_regs.h
>> @@ -0,0 +1,13 @@
>> +/* SPDX-License-Identifier: MIT */
>> +/*
>> + * Copyright © 2023 Intel Corporation
>> + */
>> +#ifndef XE_GT_ERROR_REGS_H_
>> +#define XE_GT_ERROR_REGS_H_
>> +
>> +#define _ERR_STAT_GT_COR 0x100160
>> +#define _ERR_STAT_GT_NONFATAL 0x100164
>> +#define ERR_STAT_GT_REG(x) XE_REG(_PICK_EVEN((x), \
>> + _ERR_STAT_GT_COR, \
>> + _ERR_STAT_GT_NONFATAL))
>> +#endif
>> diff --git a/drivers/gpu/drm/xe/xe_device_types.h b/drivers/gpu/drm/xe/xe_device_types.h
>> index 4e4184977709..96029d3348b3 100644
>> --- a/drivers/gpu/drm/xe/xe_device_types.h
>> +++ b/drivers/gpu/drm/xe/xe_device_types.h
>> @@ -368,6 +368,7 @@ struct xe_device {
>> /** @hardware_errors_regs: list of hw error regs*/
>> struct hardware_errors_regs {
>> const struct err_msg_cntr_pair *dev_err_stat[HARDWARE_ERROR_MAX];
>> + const struct err_msg_cntr_pair *err_stat_gt[HARDWARE_ERROR_MAX];
> same here should we make it part of struct xe_gt?
Same comment as in previous patch.
>> } hw_err_regs;
>>
>> /* private: */
>> diff --git a/drivers/gpu/drm/xe/xe_gt_types.h b/drivers/gpu/drm/xe/xe_gt_types.h
>> index 35b8c19fa8bf..5daff5c434c7 100644
>> --- a/drivers/gpu/drm/xe/xe_gt_types.h
>> +++ b/drivers/gpu/drm/xe/xe_gt_types.h
>> @@ -9,10 +9,12 @@
>> #include "xe_force_wake_types.h"
>> #include "xe_gt_idle_sysfs_types.h"
>> #include "xe_hw_engine_types.h"
>> +#include "xe_hw_error.h"
>> #include "xe_hw_fence_types.h"
>> #include "xe_reg_sr_types.h"
>> #include "xe_sa_types.h"
>> #include "xe_uc_types.h"
>> +#include "regs/xe_gt_error_regs.h"
>>
>> struct xe_exec_queue_ops;
>> struct xe_migrate;
>> @@ -346,6 +348,11 @@ struct xe_gt {
>> /** @oob: bitmap with active OOB workaroudns */
>> unsigned long *oob;
>> } wa_active;
>> +
>> + /** @gt_hw_errors: hardware errors reported for the gt */
>> + struct gt_hw_errors {
>> + unsigned long count[XE_GT_HW_ERROR_MAX];
>> + } errors;
>> };
>>
>> #endif
>> diff --git a/drivers/gpu/drm/xe/xe_hw_error.c b/drivers/gpu/drm/xe/xe_hw_error.c
>> index 357d0f962d91..10aad0c396fb 100644
>> --- a/drivers/gpu/drm/xe/xe_hw_error.c
>> +++ b/drivers/gpu/drm/xe/xe_hw_error.c
>> @@ -118,14 +118,48 @@ static const struct err_msg_cntr_pair dev_err_stat_correctable_reg[] = {
>> [1 ... 31] = {"Undefined", XE_TILE_HW_ERR_UNKNOWN_CORR},
>> };
>>
>> +static const struct err_msg_cntr_pair err_stat_gt_fatal_reg[] = {
>> + [0] = {"Undefined", XE_GT_HW_ERR_UNKNOWN_FATAL},
>> + [1] = {"Array BIST", XE_GT_HW_ERR_ARR_BIST_FATAL},
>> + [2] = {"Undefined", XE_GT_HW_ERR_UNKNOWN_FATAL},
>> + [3] = {"FPU", XE_GT_HW_ERR_FPU_FATAL},
>> + [4] = {"L3 Double", XE_GT_HW_ERR_L3_DOUB_FATAL},
>> + [5] = {"L3 ECC Checker", XE_GT_HW_ERR_L3_ECC_CHK_FATAL},
>> + [6] = {"GUC SRAM", XE_GT_HW_ERR_GUC_FATAL},
>> + [7] = {"Undefined", XE_GT_HW_ERR_UNKNOWN_FATAL},
>> + [8] = {"IDI PARITY", XE_GT_HW_ERR_IDI_PAR_FATAL},
>> + [9] = {"SQIDI", XE_GT_HW_ERR_SQIDI_FATAL},
>> + [10 ... 11] = {"Undefined", XE_GT_HW_ERR_UNKNOWN_FATAL},
>> + [12] = {"SAMPLER", XE_GT_HW_ERR_SAMPLER_FATAL},
>> + [13] = {"SLM", XE_GT_HW_ERR_SLM_FATAL},
>> + [14] = {"EU IC", XE_GT_HW_ERR_EU_IC_FATAL},
>> + [15] = {"EU GRF", XE_GT_HW_ERR_EU_GRF_FATAL},
>> + [16 ... 31] = {"Undefined", XE_GT_HW_ERR_UNKNOWN_FATAL},
>> +};
> as the fatal error path is different, these shall be enabled in the patch that enables
> fatal error processing.
Will squash patch 1 and 4. so fatal reporting will be retained here.
>> +
>> +static const struct err_msg_cntr_pair err_stat_gt_correctable_reg[] = {
>> + [0] = {"L3 SINGLE", XE_GT_HW_ERR_L3_SNG_CORR},
>> + [1] = {"SINGLE BIT GUC SRAM", XE_GT_HW_ERR_GUC_CORR},
>> + [2 ... 11] = {"Undefined", XE_GT_HW_ERR_UNKNOWN_CORR},
>> + [12] = {"SINGLE BIT SAMPLER", XE_GT_HW_ERR_SAMPLER_CORR},
>> + [13] = {"SINGLE BIT SLM", XE_GT_HW_ERR_SLM_CORR},
>> + [14] = {"SINGLE BIT EU IC", XE_GT_HW_ERR_EU_IC_CORR},
>> + [15] = {"SINGLE BIT EU GRF", XE_GT_HW_ERR_EU_GRF_CORR},
>> + [16 ... 31] = {"Undefined", XE_GT_HW_ERR_UNKNOWN_CORR},
>> +};
>> +
>> void xe_assign_hw_err_regs(struct xe_device *xe)
>> {
>> const struct err_msg_cntr_pair **dev_err_stat = xe->hw_err_regs.dev_err_stat;
>> + const struct err_msg_cntr_pair **err_stat_gt = xe->hw_err_regs.err_stat_gt;
>>
>> if (xe->info.platform == XE_DG2) {
>> dev_err_stat[HARDWARE_ERROR_CORRECTABLE] = dg2_err_stat_correctable_reg;
>> dev_err_stat[HARDWARE_ERROR_NONFATAL] = dg2_err_stat_nonfatal_reg;
>> dev_err_stat[HARDWARE_ERROR_FATAL] = dg2_err_stat_fatal_reg;
>> +
>> + err_stat_gt[HARDWARE_ERROR_CORRECTABLE] = err_stat_gt_correctable_reg;
>> + err_stat_gt[HARDWARE_ERROR_FATAL] = err_stat_gt_fatal_reg;
>> } else if (xe->info.platform == XE_PVC) {
>> dev_err_stat[HARDWARE_ERROR_CORRECTABLE] = pvc_err_stat_correctable_reg;
>> dev_err_stat[HARDWARE_ERROR_NONFATAL] = pvc_err_stat_nonfatal_reg;
>> @@ -135,9 +169,67 @@ void xe_assign_hw_err_regs(struct xe_device *xe)
>> dev_err_stat[HARDWARE_ERROR_CORRECTABLE] = dev_err_stat_correctable_reg;
>> dev_err_stat[HARDWARE_ERROR_NONFATAL] = dev_err_stat_nonfatal_reg;
>> dev_err_stat[HARDWARE_ERROR_FATAL] = dev_err_stat_fatal_reg;
>> +
>> + err_stat_gt[HARDWARE_ERROR_CORRECTABLE] = err_stat_gt_correctable_reg;
>> + err_stat_gt[HARDWARE_ERROR_FATAL] = err_stat_gt_fatal_reg;
> what platforms are targeted as part of else?
Assumption is all platforms will support GT error reporting.
>> }
>> }
>>
>> +static void
>> +xe_gt_hw_error_handler(struct xe_gt *gt, const enum hardware_error hw_err)
> the function is defined here and changed in next patch can't we have a
> common one between these.
WIll address.
>> +{
>> + const char *hw_err_str = hardware_error_type_to_str(hw_err);
>> + const struct err_msg_cntr_pair *errstat;
>> + struct hardware_errors_regs *err_regs;
>> + unsigned long errsrc;
>> + const char *errmsg;
>> + u32 indx;
>> + u32 errbit;
>> +
>> + if (gt_to_xe(gt)->info.platform == XE_PVC)
>> + return;
>> +
>> + lockdep_assert_held(>_to_xe(gt)->irq.lock);
>> + err_regs = >_to_xe(gt)->hw_err_regs;
>> + errsrc = xe_mmio_read32(gt, ERR_STAT_GT_REG(hw_err));
>> + if (!errsrc) {
>> + drm_err_ratelimited(>_to_xe(gt)->drm, HW_ERR
>> + "GT%d detected ERR_STAT_GT_REG_%s blank!\n",
>> + gt->info.id, hw_err_str);
>> + return;
>> + }
>> +
>> + drm_info(>_to_xe(gt)->drm, HW_ERR "GT%d ERR_STAT_GT_REG_%s=0x%08lx\n",
>> + gt->info.id, hw_err_str, errsrc);
> will drm_dbg makes more sense here and everywhere else to dump the register contents
Ya sure.
>> +
>> + if (hw_err == HARDWARE_ERROR_NONFATAL) {
>> + /* The GT Non Fatal Error Status Register has only reserved bits
>> + * Nothing to service.
>> + */
>> + drm_err_ratelimited(>_to_xe(gt)->drm, HW_ERR "GT%d detected %s error\n",
>> + gt->info.id, hw_err_str);
>> + goto clear_reg;
>> + }
>> +
>> + errstat = err_regs->err_stat_gt[hw_err];
>> + for_each_set_bit(errbit, &errsrc, 32) {
>> + errmsg = errstat[errbit].errmsg;
>> + indx = errstat[errbit].cntr_indx;
>> +
>> + if (hw_err == HARDWARE_ERROR_FATAL)
>> + drm_err_ratelimited(>_to_xe(gt)->drm, HW_ERR
>> + "GT%d detected %s %s error, bit[%d] is set\n",
>> + gt->info.id, errmsg, hw_err_str, errbit);
> this shall be part of last patch in the series, where the fatal errors are processed.
>> + else
>> + drm_warn(>_to_xe(gt)->drm, HW_ERR
>> + "GT%d detected %s %s error, bit[%d] is set\n",
>> + gt->info.id, errmsg, hw_err_str, errbit);
>> +
>> + gt->errors.count[indx]++;
>> + }
>> +clear_reg: xe_mmio_write32(gt, ERR_STAT_GT_REG(hw_err), errsrc);
> a new line after a label is preferred.
ok.
>> +}
>> +
>> static void
>> xe_hw_error_source_handler(struct xe_tile *tile, const enum hardware_error hw_err)
>> {
>> @@ -174,7 +266,6 @@ xe_hw_error_source_handler(struct xe_tile *tile, const enum hardware_error hw_er
>> drm_warn(&tile_to_xe(tile)->drm,
>> HW_ERR "TILE%d detected %s %s error, bit[%d] is set\n",
>> tile->id, errmsg, hw_err_str, errbit);
>> -
>> else
>> drm_err_ratelimited(&tile_to_xe(tile)->drm,
>> HW_ERR "TILE%d detected %s %s error, bit[%d] is set\n",
>> @@ -182,6 +273,9 @@ xe_hw_error_source_handler(struct xe_tile *tile, const enum hardware_error hw_er
>> tile->errors.count[indx]++;
>> }
>>
>> + if (errsrc & REG_BIT(0))
> define the BIT and use it here.
Hmm
>> + xe_gt_hw_error_handler(tile->primary_gt, hw_err);
>> +
>> xe_mmio_write32(mmio, DEV_ERR_STAT_REG(hw_err), errsrc);
>> unlock:
>> spin_unlock_irqrestore(&tile_to_xe(tile)->irq.lock, flags);
>> diff --git a/drivers/gpu/drm/xe/xe_hw_error.h b/drivers/gpu/drm/xe/xe_hw_error.h
>> index c0c05b9130eb..82c947247c27 100644
>> --- a/drivers/gpu/drm/xe/xe_hw_error.h
>> +++ b/drivers/gpu/drm/xe/xe_hw_error.h
>> @@ -51,6 +51,30 @@ enum xe_tile_hw_errors {
>> XE_TILE_HW_ERROR_MAX,
>> };
>>
>> +/* Count of GT Correctable and FATAL HW ERRORS */
>> +enum xe_gt_hw_errors {
>> + XE_GT_HW_ERR_L3_SNG_CORR,
>> + XE_GT_HW_ERR_GUC_CORR,
>> + XE_GT_HW_ERR_SAMPLER_CORR,
>> + XE_GT_HW_ERR_SLM_CORR,
>> + XE_GT_HW_ERR_EU_IC_CORR,
>> + XE_GT_HW_ERR_EU_GRF_CORR,
>> + XE_GT_HW_ERR_UNKNOWN_CORR,
>> + XE_GT_HW_ERR_ARR_BIST_FATAL,
>> + XE_GT_HW_ERR_FPU_FATAL,
>> + XE_GT_HW_ERR_L3_DOUB_FATAL,
>> + XE_GT_HW_ERR_L3_ECC_CHK_FATAL,
>> + XE_GT_HW_ERR_GUC_FATAL,
>> + XE_GT_HW_ERR_IDI_PAR_FATAL,
>> + XE_GT_HW_ERR_SQIDI_FATAL,
>> + XE_GT_HW_ERR_SAMPLER_FATAL,
>> + XE_GT_HW_ERR_SLM_FATAL,
>> + XE_GT_HW_ERR_EU_IC_FATAL,
>> + XE_GT_HW_ERR_EU_GRF_FATAL,
>> + XE_GT_HW_ERR_UNKNOWN_FATAL,
>> + XE_GT_HW_ERROR_MAX,
>> +};
> same here, define all fatals where they are actually used.
>> +
>> struct err_msg_cntr_pair {
>> const char *errmsg;
>> const u32 cntr_indx;
> Thanks,
> Aravind.
next prev parent reply other threads:[~2023-09-26 5:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 8:58 [Intel-xe] [PATCH v5 0/4] Supporting RAS on XE Himal Prasad Ghimiray
2023-08-23 8:58 ` [Intel-xe] [PATCH v5 1/4] drm/xe: Handle errors from various components Himal Prasad Ghimiray
2023-09-26 4:20 ` Aravind Iddamsetty
2023-09-26 4:57 ` Ghimiray, Himal Prasad
2023-09-26 10:09 ` Aravind Iddamsetty
2023-10-04 12:07 ` Aravind Iddamsetty
2023-10-05 4:01 ` Aravind Iddamsetty
2023-08-23 8:58 ` [Intel-xe] [PATCH v5 2/4] drm/xe: Log and count the GT hardware errors Himal Prasad Ghimiray
2023-09-26 4:20 ` Aravind Iddamsetty
2023-09-26 5:08 ` Ghimiray, Himal Prasad [this message]
2023-08-23 8:58 ` [Intel-xe] [PATCH v5 3/4] drm/xe: Support GT hardware error reporting for PVC Himal Prasad Ghimiray
2023-09-26 4:21 ` Aravind Iddamsetty
2023-09-26 5:11 ` Ghimiray, Himal Prasad
2023-08-23 8:58 ` [Intel-xe] [PATCH v5 4/4] drm/xe: Process fatal hardware errors Himal Prasad Ghimiray
2023-09-26 4:21 ` Aravind Iddamsetty
2023-09-26 10:24 ` Ghimiray, Himal Prasad
2023-08-23 9:00 ` [Intel-xe] ✓ CI.Patch_applied: success for Supporting RAS on XE (rev4) Patchwork
2023-08-23 9:00 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-23 9:01 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-23 9:05 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-23 9:05 ` [Intel-xe] ✗ CI.Hooks: 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=ed406599-055d-4189-85e4-6232f5e8d127@intel.com \
--to=himal.prasad.ghimiray@intel.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=matthew.d.roper@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