From: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@Intel.com>
To: sashiko-reviews@lists.linux.dev
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v4 10/12] drm/xe/lmtt: Report invalidation errors using structured xe_log API
Date: Tue, 29 Sep 2026 10:22:49 +0530 [thread overview]
Message-ID: <77862b03-640a-49e3-a7a7-82cddb106b05@Intel.com> (raw)
In-Reply-To: <20260928093659.4A08F1F000FF@smtp.kernel.org>
On 28-Sep-26 3:06 PM, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] xe_lmtt: missing newline in xe_log_err format string
> --
>
> commit d8b97ea5041b192b44dac80a8e9209e9058d6519
> Author: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
>
> drm/xe/lmtt: Report invalidation errors using structured xe_log API
>
> This commit replaces xe_tile_sriov_err() with xe_log_err() using the LMTT
> component tag for LMTT and MERT invalidation failures. It preserves the
> SR-IOV prefix in the newly structured log messages.
>
>> diff --git a/drivers/gpu/drm/xe/xe_lmtt.c b/drivers/gpu/drm/xe/xe_lmtt.c
>> index 0c726eda93906..fe77b3ec06807 100644
>> --- a/drivers/gpu/drm/xe/xe_lmtt.c
>> +++ b/drivers/gpu/drm/xe/xe_lmtt.c
>
> [ ... ]
>
>> @@ -302,14 +303,15 @@ void xe_lmtt_invalidate_hw(struct xe_lmtt *lmtt)
>>
>> err = lmtt_invalidate_hw(lmtt);
>> if (err)
>> - xe_tile_sriov_err(tile, "LMTT invalidation failed (%pe)",
>> - ERR_PTR(err));
>> + xe_log_err(tile, LMTT, err, "%s invalidation failed.",
>> + xe_sriov_printk_prefix(xe));
>
> [Severity: Low]
> Does this format string need a trailing newline?
>
> Without a trailing '\n' in xe_log_err(), the kernel printk system might leave
> the log line unterminated, potentially causing subsequent logs to be
> concatenated to this line.
Noted,I will update in the next patch.
>> if (xe_device_has_mert(xe) && xe_tile_is_root(tile)) {
>> err = xe_mert_invalidate_lmtt(xe);
>> if (err)
>> - xe_tile_sriov_err(tile, "MERT LMTT invalidation failed (%pe)",
>> - ERR_PTR(err));
>> + xe_log_err(tile, LMTT, err,
>> + "%s MERT invalidation failed.\n",
>> + xe_sriov_printk_prefix(xe));
>> }
>> }
>
next prev parent reply other threads:[~2026-09-29 4:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 9:21 [PATCH v4 00/12] drm/xe: Convert IO_BUS errors to structured xe_log API Dnyaneshwar Bhadane
2026-09-28 9:21 ` [PATCH v4 01/12] drm/xe/log: Add VRAM, PAT, and HWMON DRIVER_HARDWARE components Dnyaneshwar Bhadane
2026-09-28 9:21 ` [PATCH v4 02/12] drm/xe/ggtt: Report GGTT errors using structured logging Dnyaneshwar Bhadane
2026-09-29 5:15 ` Mallesh, Koujalagi
2026-09-28 9:21 ` [PATCH v4 03/12] drm/xe/hwmon: Report errors using structured xe_log API Dnyaneshwar Bhadane
2026-09-29 5:25 ` Mallesh, Koujalagi
2026-09-28 9:21 ` [PATCH v4 04/12] drm/xe/mmio: Report BAR mapping " Dnyaneshwar Bhadane
2026-09-29 5:34 ` Mallesh, Koujalagi
2026-10-01 9:50 ` Dnyaneshwar Bhadane
2026-09-28 9:21 ` [PATCH v4 05/12] drm/xe/memirq: Report " Dnyaneshwar Bhadane
2026-09-28 9:30 ` sashiko-bot
2026-09-28 12:32 ` Bhadane, Dnyaneshwar
2026-09-29 5:40 ` Mallesh, Koujalagi
2026-09-28 9:21 ` [PATCH v4 06/12] drm/xe/reg_sr: Report save-restore " Dnyaneshwar Bhadane
2026-09-28 9:31 ` sashiko-bot
2026-09-28 12:35 ` Bhadane, Dnyaneshwar
2026-09-28 9:21 ` [PATCH v4 07/12] drm/xe/pat: Return error from xe_pat_init_early() on unknown platform Dnyaneshwar Bhadane
2026-09-29 5:58 ` Mallesh, Koujalagi
2026-09-28 9:21 ` [PATCH v4 08/12] drm/xe/pat: Report missing PAT table using structured xe_log API Dnyaneshwar Bhadane
2026-09-28 9:21 ` [PATCH v4 09/12] drm/xe/pci: Report unknown GMDID versions " Dnyaneshwar Bhadane
2026-09-29 6:34 ` Mallesh, Koujalagi
2026-09-28 9:21 ` [PATCH v4 10/12] drm/xe/lmtt: Report invalidation errors " Dnyaneshwar Bhadane
2026-09-28 9:36 ` sashiko-bot
2026-09-29 4:51 ` Dnyaneshwar Bhadane
2026-09-29 4:52 ` Dnyaneshwar Bhadane [this message]
2026-09-30 8:36 ` Mallesh, Koujalagi
2026-09-28 9:21 ` [PATCH v4 11/12] drm/xe/vram: Report tile vs device VRAM visibility errors Dnyaneshwar Bhadane
2026-09-28 9:21 ` [PATCH v4 12/12] drm/xe/vram: Report VRAM errors using structured xe_log API Dnyaneshwar Bhadane
2026-09-28 9:33 ` sashiko-bot
2026-09-30 6:48 ` Mallesh, Koujalagi
2026-10-07 20:20 ` Dnyaneshwar Bhadane
2026-09-28 16:14 ` ✓ CI.KUnit: success for drm/xe: Convert IO_BUS errors to structured xe_log API (rev4) Patchwork
2026-09-28 16:53 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-28 20:42 ` ✗ Xe.CI.FULL: 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=77862b03-640a-49e3-a7a7-82cddb106b05@Intel.com \
--to=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