From: sashiko-bot@kernel.org
To: "Umesh Nerlige Ramappa" <umesh.nerlige.ramappa@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v4 5/7] drm/xe/uc: Report DMA failure using SIGID
Date: Fri, 18 Sep 2026 00:07:16 +0000 [thread overview]
Message-ID: <20260918000717.6DFBB1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260917235923.1521112-14-umesh.nerlige.ramappa@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] xe: missing conversion of DMA failure message to xe_log_err() in uc_fw_xfer()
--
commit 519565d5579d72f99be56f54099a18eadbbceb69
Author: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
drm/xe/uc: Report DMA failure using SIGID
Convert the uC DMA failure error to use the xe_log_err() helper.
> diff --git a/drivers/gpu/drm/xe/xe_uc_fw.c b/drivers/gpu/drm/xe/xe_uc_fw.c
> index a8e6f18cc9b4a..21e2c1be08842 100644
> --- a/drivers/gpu/drm/xe/xe_uc_fw.c
> +++ b/drivers/gpu/drm/xe/xe_uc_fw.c
[ ... ]
> @@ -927,9 +932,11 @@ int xe_uc_fw_upload(struct xe_uc_fw *uc_fw, u32 offset, u32 dma_flags)
> return 0;
>
> fail:
> - drm_err(&xe->drm, "Failed to load %s firmware %s (%d)\n",
> - xe_uc_fw_type_repr(uc_fw->type), uc_fw->path,
> - err);
> + if (uc_fw->type == XE_UC_FW_TYPE_GUC)
> + xe_log_err(gt, GUC, err, "Failed to load firmware %s\n", uc_fw->path);
> + else
> + xe_log_err(gt, HUC, err, "Failed to load firmware %s\n", uc_fw->path);
> +
[Severity: Medium]
Does this commit match its description? The commit message explicitly claims
to "Convert the uC DMA failure error to use the xe_log_err() helper."
While it did convert the generic firmware load failure message here in
xe_uc_fw_upload(), it entirely missed the actual DMA-specific error message
in uc_fw_xfer():
if (ret)
drm_err(&xe->drm, "DMA for %s fw failed, DMA_CTRL=%u\n",
xe_uc_fw_type_repr(uc_fw->type), dma_ctrl);
If the uC firmware DMA transfer fails (e.g., timeout in xe_mmio_wait32), the
error is still logged using the old drm_err() format without the intended
SIGID logging.
> xe_uc_fw_change_status(uc_fw, XE_UC_FIRMWARE_LOAD_FAIL);
> return err;
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260917235923.1521112-9-umesh.nerlige.ramappa@intel.com?part=5
next prev parent reply other threads:[~2026-09-18 0:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 23:59 [PATCH v4 0/7] Use SIG_ID logs for GuC component Umesh Nerlige Ramappa
2026-09-17 23:59 ` [PATCH v4 1/7] drm/xe/guc: Use different error codes for GuC load errors Umesh Nerlige Ramappa
2026-09-17 23:59 ` [PATCH v4 2/7] drm/xe/guc: Handle CRASH and EXCEPTION G2H with separate helpers Umesh Nerlige Ramappa
2026-09-18 0:08 ` sashiko-bot
2026-09-17 23:59 ` [PATCH v4 3/7] drm/xe/guc: Make ct_dead_capture available on non-debug config Umesh Nerlige Ramappa
2026-09-18 0:06 ` sashiko-bot
2026-09-17 23:59 ` [PATCH v4 4/7] drm/xe/guc: Cleanup error codes and handling for CT errors Umesh Nerlige Ramappa
2026-09-18 0:17 ` sashiko-bot
2026-09-17 23:59 ` [PATCH v4 5/7] drm/xe/uc: Report DMA failure using SIGID Umesh Nerlige Ramappa
2026-09-18 0:07 ` sashiko-bot [this message]
2026-09-17 23:59 ` [PATCH v4 6/7] drm/xe/guc: Report major GuC failures " Umesh Nerlige Ramappa
2026-09-17 23:59 ` [PATCH v4 7/7] drm/xe/guc: Report errors that cause a CT shutdown " Umesh Nerlige Ramappa
2026-09-18 0:08 ` sashiko-bot
2026-09-18 0:58 ` ✗ CI.KUnit: failure for Use SIG_ID logs for GuC component (rev3) 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=20260918000717.6DFBB1F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=umesh.nerlige.ramappa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.