From: "Mallesh, Koujalagi" <mallesh.koujalagi@intel.com>
To: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v5 03/12] drm/xe/hwmon: Report errors using structured xe_log API
Date: Thu, 8 Oct 2026 18:31:04 +0530 [thread overview]
Message-ID: <24e55f60-bcd2-42d0-a4d0-0664fcca2a80@intel.com> (raw)
In-Reply-To: <20261007211417.2093611-4-dnyaneshwar.bhadane@intel.com>
On 08-10-2026 02: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:
>
> Signed-off-by: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
LGTM,
Reviewed-by: Mallesh Koujalagi <mallesh.koujalagi@intel.com>
> ---
> v2:
> - Store error in local variable err (Mallesh)
> ---
> ---
> drivers/gpu/drm/xe/xe_hwmon.c | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_hwmon.c b/drivers/gpu/drm/xe/xe_hwmon.c
> index 5edeac961ec3..fa5473ed6e7f 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",
> + channel, power_attr, reg_val);
> reg_val = 0;
> }
> } else {
> @@ -1563,7 +1564,7 @@ int xe_hwmon_register(struct xe_device *xe)
> {
> struct device *dev = xe->drm.dev;
> struct xe_hwmon *hwmon;
> - int ret;
> + int ret, err;
>
> /* hwmon is available only for dGfx */
> if (!IS_DGFX(xe))
> @@ -1594,9 +1595,11 @@ 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);
> + err = PTR_ERR(hwmon->hwmon_dev);
> + xe_log_err(xe, HWMON, err,
> + "Failed to register xe hwmon\n");
> xe->hwmon = NULL;
> - return PTR_ERR(hwmon->hwmon_dev);
> + return err;
> }
>
> return 0;
next prev parent reply other threads:[~2026-10-08 13:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 21:14 [PATCH v5 00/12] drm/xe: Convert IO_BUS errors to structured xe_log API Dnyaneshwar Bhadane
2026-10-07 21:14 ` [PATCH v5 01/12] drm/xe/log: Add VRAM, PAT, and HWMON DRIVER_HARDWARE components Dnyaneshwar Bhadane
2026-10-08 13:59 ` Mallesh, Koujalagi
2026-10-07 21:14 ` [PATCH v5 02/12] drm/xe/ggtt: Report GGTT errors using structured logging Dnyaneshwar Bhadane
2026-10-07 21:14 ` [PATCH v5 03/12] drm/xe/hwmon: Report errors using structured xe_log API Dnyaneshwar Bhadane
2026-10-08 13:01 ` Mallesh, Koujalagi [this message]
2026-10-07 21:14 ` [PATCH v5 04/12] drm/xe/mmio: Report BAR mapping " Dnyaneshwar Bhadane
2026-10-07 21:14 ` [PATCH v5 05/12] drm/xe/memirq: Report " Dnyaneshwar Bhadane
2026-10-07 21:20 ` sashiko-bot
2026-10-07 21:14 ` [PATCH v5 06/12] drm/xe/reg_sr: Report save-restore " Dnyaneshwar Bhadane
2026-10-07 21:23 ` sashiko-bot
2026-10-08 13:45 ` Mallesh, Koujalagi
2026-10-07 21:14 ` [PATCH v5 07/12] drm/xe/pat: Return error from xe_pat_init_early() on unknown platform Dnyaneshwar Bhadane
2026-10-07 21:14 ` [PATCH v5 08/12] drm/xe/pat: Report missing PAT table using structured xe_log API Dnyaneshwar Bhadane
2026-10-07 21:14 ` [PATCH v5 09/12] drm/xe/pci: Report unknown GMDID versions " Dnyaneshwar Bhadane
2026-10-07 21:14 ` [PATCH v5 10/12] drm/xe/lmtt: Report invalidation errors " Dnyaneshwar Bhadane
2026-10-08 13:07 ` Mallesh, Koujalagi
2026-10-07 21:14 ` [PATCH v5 11/12] drm/xe/vram: Report tile vs device VRAM visibility errors Dnyaneshwar Bhadane
2026-10-08 13:25 ` Mallesh, Koujalagi
2026-10-09 10:42 ` Bhadane, Dnyaneshwar
2026-10-07 21:14 ` [PATCH v5 12/12] drm/xe/vram: Report VRAM errors using structured xe_log API Dnyaneshwar Bhadane
2026-10-07 21:19 ` sashiko-bot
2026-10-07 21:40 ` ✗ CI.checkpatch: warning for drm/xe: Convert IO_BUS errors to structured xe_log API (rev5) Patchwork
2026-10-07 21:42 ` ✓ CI.KUnit: success " Patchwork
2026-10-07 22:32 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-08 2:59 ` ✗ 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=24e55f60-bcd2-42d0-a4d0-0664fcca2a80@intel.com \
--to=mallesh.koujalagi@intel.com \
--cc=dnyaneshwar.bhadane@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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