From: sashiko-bot@kernel.org
To: "Dnyaneshwar Bhadane" <dnyaneshwar.bhadane@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v6 06/12] drm/xe/reg_sr: Report save-restore errors using structured xe_log API
Date: Mon, 12 Oct 2026 05:28:44 +0000 [thread overview]
Message-ID: <sashiko-outbox-167666@kernel.org> (raw)
In-Reply-To: <20261012051823.2201360-7-dnyaneshwar.bhadane@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] drm/xe: incomplete refactoring missing xe_gt_err() replacement in xe_reg_sr_add
--
commit 81903de8af1b2d3214fd6a5c1628dc2db69e9354
Author: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
drm/xe/reg_sr: Report save-restore errors using structured xe_log API
This commit replaces xe_gt_notice() and xe_gt_err() calls with xe_log_info()
and xe_log_err() for register save-restore operations.
> diff --git a/drivers/gpu/drm/xe/xe_reg_sr.c b/drivers/gpu/drm/xe/xe_reg_sr.c
> index e328f50725572..eab84a528d122 100644
> --- a/drivers/gpu/drm/xe/xe_reg_sr.c
> +++ b/drivers/gpu/drm/xe/xe_reg_sr.c
[ ... ]
> @@ -219,7 +220,7 @@ void xe_reg_sr_apply_mmio(struct xe_reg_sr *sr, struct xe_gt *gt)
>
> CLASS(xe_force_wake, fw_ref)(gt_to_fw(gt), XE_FORCEWAKE_ALL);
> if (!xe_force_wake_ref_has_domain(fw_ref.domains, XE_FORCEWAKE_ALL)) {
> - xe_gt_err(gt, "Failed to apply, err=-ETIMEDOUT\n");
> + xe_log_err(gt, REGS, -ETIMEDOUT, "Failed to apply\n");
> return;
> }
>
[Severity: Medium]
Does this commit miss replacing the xe_gt_err() call in xe_reg_sr_add()?
If xe_reg_sr_add() fails (e.g., due to an incompatible entry or memory
allocation failure), it still calls the legacy macro instead of the new
xe_log_err() API:
drivers/gpu/drm/xe/xe_reg_sr.c:xe_reg_sr_add() {
...
fail:
xe_gt_err(gt,
"discarding save-restore reg %04lx (clear: %08x, set: %08x, masked: %s, mcr: %s): ret=%d\n",
idx, e->clr_bits, e->set_bits,
str_yes_no(e->reg.masked),
str_yes_no(e->reg.mcr),
ret);
reg_sr_inc_error(sr);
return ret;
}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261012051823.2201360-1-dnyaneshwar.bhadane@intel.com?part=6
next prev parent reply other threads:[~2026-10-12 5:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 5:18 [PATCH v6 00/12] drm/xe: Convert IO_BUS errors to structured xe_log API Dnyaneshwar Bhadane
2026-10-12 5:18 ` [PATCH v6 01/12] drm/xe/log: Add VRAM, PAT, and HWMON DRIVER_HARDWARE components Dnyaneshwar Bhadane
2026-10-12 5:18 ` [PATCH v6 02/12] drm/xe/ggtt: Report GGTT errors using structured logging Dnyaneshwar Bhadane
2026-10-12 5:18 ` [PATCH v6 03/12] drm/xe/hwmon: Report errors using structured xe_log API Dnyaneshwar Bhadane
2026-10-12 5:18 ` [PATCH v6 04/12] drm/xe/mmio: Report BAR mapping " Dnyaneshwar Bhadane
2026-10-12 5:18 ` [PATCH v6 05/12] drm/xe/memirq: Report " Dnyaneshwar Bhadane
2026-10-12 5:18 ` [PATCH v6 06/12] drm/xe/reg_sr: Report save-restore " Dnyaneshwar Bhadane
2026-10-12 5:28 ` sashiko-bot [this message]
2026-10-12 5:18 ` [PATCH v6 07/12] drm/xe/pat: Return error from xe_pat_init_early() on unknown platform Dnyaneshwar Bhadane
2026-10-12 5:18 ` [PATCH v6 08/12] drm/xe/pat: Report missing PAT table using structured xe_log API Dnyaneshwar Bhadane
2026-10-12 5:18 ` [PATCH v6 09/12] drm/xe/pci: Report unknown GMDID versions " Dnyaneshwar Bhadane
2026-10-12 5:18 ` [PATCH v6 10/12] drm/xe/lmtt: Report invalidation errors " Dnyaneshwar Bhadane
2026-10-12 5:18 ` [PATCH v6 11/12] drm/xe/vram: Report tile vs device VRAM visibility errors Dnyaneshwar Bhadane
2026-10-12 9:01 ` Mallesh, Koujalagi
2026-10-12 5:18 ` [PATCH v6 12/12] drm/xe/vram: Report VRAM errors using structured xe_log API Dnyaneshwar Bhadane
2026-10-12 5:30 ` sashiko-bot
2026-10-12 9:08 ` Mallesh, Koujalagi
2026-10-12 5:48 ` ✓ CI.KUnit: success for drm/xe: Convert IO_BUS errors to structured xe_log API (rev6) Patchwork
2026-10-12 6:38 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-12 7:58 ` ✓ Xe.CI.FULL: " 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=sashiko-outbox-167666@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dnyaneshwar.bhadane@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