Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nilawar, Badal" <badal.nilawar@intel.com>
To: <sashiko-reviews@lists.linux.dev>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v4 01/12] drm/xe/cper: Add CPER reporting entry point for xe_log
Date: Fri, 9 Oct 2026 17:47:26 +0530	[thread overview]
Message-ID: <5d3e5c5c-00a2-4628-a93f-d538da5c064d@intel.com> (raw)
In-Reply-To: <sashiko-outbox-165258@kernel.org>


On 09-10-2026 16:13, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] drm/xe: Silent telemetry loss when hardware SIGIDs lack exact RAS data payload
> --
>
> commit a8ad6417f3a91a193b5e9bf972e9a0e60ff46e5a
> Author: Badal Nilawar <badal.nilawar@intel.com>
>
> drm/xe/cper: Add CPER reporting entry point for xe_log
>
> Introduce xe_cper_emit() as the single entry point for emitting
> CPER records from xe_log. Hardware SIGIDs are routed to a hardware
> error helper, and software SIGIDs are left as TODO.
>
>> diff --git a/drivers/gpu/drm/xe/xe_cper.c b/drivers/gpu/drm/xe/xe_cper.c
>> new file mode 100644
>> index 0000000000000..c5caa0e8f496a
>> --- /dev/null
>> +++ b/drivers/gpu/drm/xe/xe_cper.c
> [ ... ]
>> +void xe_cper_emit(struct xe_device *xe, int cper_sev, enum xe_sigid sigid,
>> +		  u32 component, u32 location, const void *data, size_t len,
>> +		  struct va_format *vaf)
>> +{
>> +	if (!xe)
>> +		return;
>> +
>> +	if (is_hw_sigid(sigid)) {
>> +		if (!IS_ERR_OR_NULL(data) && len == sizeof(struct xe_ras_error_class))
>> +			xe_cper_emit_hw_err(xe, cper_sev, sigid, data);
>> +		return;
> [Severity: Medium]
> If a hardware SIGID log entry is missing the expected RAS data payload (e.g.,
> the data pointer is ERR_PTR, NULL, or the length is unexpected), does this
> unconditionally return and drop the telemetry?
>
> Since there is no fallback to emit a software CPER log or print a warning,
> it looks like this could result in a silent loss of hardware error data.

The log entry is not lost: __xe_log_emit() emits the dmesg entry before 
the CPER path, so the hardware error is always reported in dmesg.

A hardware CPER record is built from the firmware error counter, which 
requires the RAS error class; without it there is no meaningful record 
to emit.

All hardware SIGID users (xe_ras.c) pass the error class, so this path 
is only a guard against misuse.

Thanks,
Badal

>
>> +	}
>> +
>> +	/* TODO software CPER */
>> +}

  reply	other threads:[~2026-10-09 12:17 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 10:46 [PATCH v4 00/12] Add CPER logging support for CRI Badal Nilawar
2026-10-09 10:46 ` [PATCH v4 01/12] drm/xe/cper: Add CPER reporting entry point for xe_log Badal Nilawar
2026-10-09 10:43   ` sashiko-bot
2026-10-09 12:17     ` Nilawar, Badal [this message]
2026-10-12  6:18   ` Raag Jadav
2026-10-09 10:46 ` [PATCH v4 02/12] drm/xe/cper: Retrieve the error counter record for CPER reporting Badal Nilawar
2026-10-09 10:46   ` sashiko-bot
2026-10-09 12:27     ` Nilawar, Badal
2026-10-12  9:07   ` Raag Jadav
2026-10-09 10:46 ` [PATCH v4 03/12] drm/xe/cper: Initialize Intel-specific error section header Badal Nilawar
2026-10-09 10:46 ` [PATCH v4 04/12] drm/xe/cper: Construct CPER record for hardware errors Badal Nilawar
2026-10-09 10:46 ` [PATCH v4 05/12] drm/xe/xe_ras: Add support to retrieve info queue data for CRI Badal Nilawar
2026-10-09 10:40   ` sashiko-bot
2026-10-09 12:45     ` Nilawar, Badal
2026-10-09 10:46 ` [PATCH v4 06/12] drm/xe/cper: Prepare Intel CPER error info records Badal Nilawar
2026-10-09 10:41   ` sashiko-bot
2026-10-09 13:07     ` Nilawar, Badal
2026-10-09 10:46 ` [PATCH v4 07/12] drm/xe/cper: Log CPER records for aggregate counter retrieval Badal Nilawar
2026-10-09 10:46 ` [PATCH v4 08/12] drm/xe/cper: Emit cper record to trace buf Badal Nilawar
2026-10-09 10:38   ` sashiko-bot
2026-10-09 10:46 ` [PATCH v4 09/12] drm/xe/xe_ras: Report device memory errors using SIGID Badal Nilawar
2026-10-09 10:46 ` [PATCH v4 10/12] drm/xe/xe_ras: Report core compute " Badal Nilawar
2026-10-09 10:46 ` [PATCH v4 11/12] drm/xe/xe_ras: Report soc internal " Badal Nilawar
2026-10-09 10:46 ` [PATCH v4 12/12] drm/xe/xe_ras: Report correctable " Badal Nilawar
2026-10-09 10:50   ` sashiko-bot
2026-10-09 10:54 ` ✗ CI.checkpatch: warning for Add CPER logging support for CRI (rev4) Patchwork
2026-10-09 10:56 ` ✓ CI.KUnit: success " Patchwork
2026-10-09 12:03 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-10-09 15:13 ` ✓ Xe.CI.FULL: success " Patchwork
2026-10-12  6:14 ` [PATCH v4 00/12] Add CPER logging support for CRI Raag Jadav

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=5d3e5c5c-00a2-4628-a93f-d538da5c064d@intel.com \
    --to=badal.nilawar@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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