From: "Mallesh, Koujalagi" <mallesh.koujalagi@intel.com>
To: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>,
<intel-xe@lists.freedesktop.org>
Cc: <michal.wajdeczko@intel.com>
Subject: Re: [PATCH v4 03/12] drm/xe/hwmon: Report errors using structured xe_log API
Date: Tue, 29 Sep 2026 10:55:25 +0530 [thread overview]
Message-ID: <bd011660-a6de-49ac-91ec-a8c01ed9896a@intel.com> (raw)
In-Reply-To: <20260928092114.1610203-4-dnyaneshwar.bhadane@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1960 bytes --]
On 28-09-2026 02:51 pm, Dnyaneshwar Bhadane wrote:
> Replace drm_err() calls with xe_log_err() using the HWMON component
> tag to enable structured error reporting with SIGID for hardware
> monitor failures:
>
> Signed-off-by: Dnyaneshwar Bhadane<dnyaneshwar.bhadane@intel.com>
> ---
> drivers/gpu/drm/xe/xe_hwmon.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_hwmon.c b/drivers/gpu/drm/xe/xe_hwmon.c
> index 5edeac961ec3..dbeb32d748e6 100644
> --- a/drivers/gpu/drm/xe/xe_hwmon.c
> +++ b/drivers/gpu/drm/xe/xe_hwmon.c
> @@ -15,6 +15,7 @@
> #include "regs/xe_pcode_regs.h"
> #include "xe_device.h"
> #include "xe_hwmon.h"
> +#include "xe_log.h"
> #include "xe_mmio.h"
> #include "xe_pcode.h"
> #include "xe_pcode_api.h"
> @@ -558,9 +559,9 @@ xe_hwmon_power_max_interval_show(struct device *dev, struct device_attribute *at
> if (hwmon->xe->info.has_mbx_power_limits) {
> ret = xe_hwmon_pcode_read_power_limit(hwmon, power_attr, channel, ®_val);
> if (ret) {
> - drm_err(&hwmon->xe->drm,
> - "power interval read fail, ch %d, attr %d, val 0x%08x, ret %d\n",
> - channel, power_attr, reg_val, ret);
> + xe_log_err(hwmon->xe, HWMON, ret,
> + "power interval read fail, ch %d, attr %d, val 0x%08x\n",
Message should start with small or capital make it consistency.
> + channel, power_attr, reg_val);
> reg_val = 0;
> }
> } else {
> @@ -1594,7 +1595,8 @@ int xe_hwmon_register(struct xe_device *xe)
> &hwmon_chip_info,
> hwmon_groups);
> if (IS_ERR(hwmon->hwmon_dev)) {
> - drm_err(&xe->drm, "Failed to register xe hwmon (%pe)\n", hwmon->hwmon_dev);
> + xe_log_err(xe, HWMON, PTR_ERR(hwmon->hwmon_dev),
> + "Failed to register xe hwmon\n");
> xe->hwmon = NULL;
> return PTR_ERR(hwmon->hwmon_dev);
Make use of local variable err, like int err = PTR_ERR(hwmon->hwmon_dev);
Thanks,
-/Mallesh
> }
[-- Attachment #2: Type: text/html, Size: 2900 bytes --]
next prev parent reply other threads:[~2026-09-29 5:25 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 [this message]
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
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=bd011660-a6de-49ac-91ec-a8c01ed9896a@intel.com \
--to=mallesh.koujalagi@intel.com \
--cc=dnyaneshwar.bhadane@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.wajdeczko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox