From: sashiko-bot@kernel.org
To: "Arvind Yadav" <arvind.yadav@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v3 1/1] drm/xe/guc: Report reset-request failure using SIGID
Date: Mon, 24 Aug 2026 07:27:45 +0000 [thread overview]
Message-ID: <20260824072745.D9DC21F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260824071749.1345374-2-arvind.yadav@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The patch introduces a build breakage by referencing a non-existent header file (`xe_log.h`) and an undefined macro (`xe_log_err`). Additionally, it fails to implement the behavior promised in the commit message by passing the standard error code `-EIO` instead of the specified identifier `XE_SIGID_GT_TDR`.
--
--- Patch [1]: [PATCH v3 1/1] drm/xe/guc: Report reset-request failure using SIGID ---
commit 67003dc14864f3bc207ea53dfd2f7eb0b4972a51
Author: Arvind Yadav <arvind.yadav@intel.com>
drm/xe/guc: Report reset-request failure using SIGID
Route the GuC engine reset-request failure through the structured SIGID
logging helper.
> This path was already reported as an error and triggers GT reset recovery,
> so use the GT component and report it with XE_SIGID_GT_TDR.
[Severity: Medium]
The commit message mentions reporting the error with XE_SIGID_GT_TDR, but the
code below passes -EIO instead.
> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
> index 864859bd0ccc9..0faeecc7c516d 100644
> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> @@ -34,6 +34,7 @@
> #include "xe_guc_klv_helpers.h"
> #include "xe_guc_submit_types.h"
> #include "xe_hw_engine.h"
> +#include "xe_log.h"
[Severity: Medium]
Could this introduce a build breakage? It appears xe_log.h does not exist in
the repository.
[ ... ]
> @@ -3360,8 +3361,9 @@ int xe_guc_exec_queue_reset_failure_handler(struct xe_guc *guc, u32 *msg, u32 len
> reason = msg[2];
>
> /* Unexpected failure of a hardware feature, log an actual error */
> - xe_gt_err(gt, "GuC engine reset request failed on %d:%d because 0x%08X",
> - guc_class, instance, reason);
> + xe_log_err(gt, GT, -EIO,
> + "GuC engine reset request failed on %d:%d because 0x%08X\n",
> + guc_class, instance, reason);
[Severity: Medium]
Is xe_log_err defined anywhere since xe_log.h is missing? It looks like this
might result in an undefined macro error during compilation.
Additionally, as noted above, this passes -EIO instead of the promised
XE_SIGID_GT_TDR identifier.
>
> xe_gt_reset_async(gt);
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260824071749.1345374-2-arvind.yadav@intel.com?part=1
prev parent reply other threads:[~2026-08-24 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 7:17 [PATCH v3 0/1] drm/xe: Report GT TDR and VM rebind faults using SIGID Arvind Yadav
2026-08-24 7:17 ` [PATCH v3 1/1] drm/xe/guc: Report reset-request failure " Arvind Yadav
2026-08-24 7:27 ` sashiko-bot [this message]
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=20260824072745.D9DC21F00A3D@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=arvind.yadav@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 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.