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 03/12] drm/xe/hwmon: Report errors using structured xe_log API
Date: Wed, 26 Aug 2026 15:20:15 +0530 [thread overview]
Message-ID: <e5a77bae-9e0f-4603-816b-35529d6c58bd@intel.com> (raw)
In-Reply-To: <20260819191442.1957986-4-dnyaneshwar.bhadane@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2095 bytes --]
On 20-08-2026 12:44 am, 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:
nit: '.' rigtht?
>
> 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 5284cab6703d..9ff351e87e5a 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"
> @@ -563,9 +564,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, -EIO,
Use ret as errno.
> + "power interval read fail, ch %d, attr %d, val 0x%08x, ret %d\n",
> + channel, power_attr, reg_val, ret);
Once you pass ret as errno, no need to log it.
> reg_val = 0;
> }
> } else {
> @@ -1599,7 +1600,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, -EIO,
hmm, is -EIO correct one? we can use PTR_ERR(hwmon->hwmon_dev) right?
> + "Failed to register xe hwmon (%pe)", hwmon->hwmon_dev);
nit: Once we pass correct errno, no need to log so remove hwmon->hwmon_dev.
nit: add '\n' end of message
Thanks,
-/Mallesh
> xe->hwmon = NULL;
> return PTR_ERR(hwmon->hwmon_dev);
> }
[-- Attachment #2: Type: text/html, Size: 3547 bytes --]
next prev parent reply other threads:[~2026-08-26 9:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 19:14 [PATCH 00/12] drm/xe: Convert IO_BUS errors to structured xe_log API Dnyaneshwar Bhadane
2026-08-19 19:14 ` [PATCH 01/12] drm/xe/log: Add VRAM, PAT, and HWMON DRIVER_HARDWARE components Dnyaneshwar Bhadane
2026-08-19 19:14 ` [PATCH 02/12] drm/xe/ggtt: Report GGTT errors using structured logging Dnyaneshwar Bhadane
2026-08-19 19:14 ` [PATCH 03/12] drm/xe/hwmon: Report errors using structured xe_log API Dnyaneshwar Bhadane
2026-08-19 19:23 ` sashiko-bot
2026-08-26 9:50 ` Mallesh, Koujalagi [this message]
2026-08-19 19:14 ` [PATCH 04/12] drm/xe/mmio: Report BAR mapping " Dnyaneshwar Bhadane
2026-08-19 19:14 ` [PATCH 05/12] drm/xe/memirq: Report " Dnyaneshwar Bhadane
2026-08-19 19:22 ` sashiko-bot
2026-08-26 10:09 ` Mallesh, Koujalagi
2026-08-19 19:14 ` [PATCH 06/12] drm/xe/reg_whitelist: Report whitelist overflow " Dnyaneshwar Bhadane
2026-08-19 19:22 ` sashiko-bot
2026-08-26 10:22 ` Mallesh, Koujalagi
2026-08-19 19:14 ` [PATCH 07/12] drm/xe/reg_sr: Report save-restore errors " Dnyaneshwar Bhadane
2026-08-26 12:33 ` Mallesh, Koujalagi
2026-08-19 19:14 ` [PATCH 08/12] drm/xe/pat: Assert pat.ops before dereferencing members Dnyaneshwar Bhadane
2026-08-19 19:22 ` sashiko-bot
2026-08-19 19:14 ` [PATCH 09/12] drm/xe/pat: Report missing PAT table using structured xe_log API Dnyaneshwar Bhadane
2026-08-19 19:23 ` sashiko-bot
2026-08-19 19:14 ` [PATCH 10/12] drm/xe/pci: Report unknown GMDID versions " Dnyaneshwar Bhadane
2026-08-19 19:27 ` sashiko-bot
2026-08-19 19:14 ` [PATCH 11/12] drm/xe/lmtt: Report invalidation errors " Dnyaneshwar Bhadane
2026-08-19 19:28 ` sashiko-bot
2026-08-26 10:29 ` Mallesh, Koujalagi
2026-08-19 19:14 ` [PATCH 12/12] drm/xe/vram: Report VRAM " Dnyaneshwar Bhadane
2026-08-19 19:29 ` sashiko-bot
2026-08-20 6:06 ` Dnyaneshwar Bhadane
2026-08-19 19:23 ` ✓ CI.KUnit: success for drm/xe: Convert IO_BUS errors to " Patchwork
2026-08-19 20:45 ` ✓ Xe.CI.BAT: " Patchwork
2026-08-20 1:38 ` ✗ 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=e5a77bae-9e0f-4603-816b-35529d6c58bd@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