From: Raag Jadav <raag.jadav@intel.com>
To: Karthik Poosa <karthik.poosa@intel.com>
Cc: intel-xe@lists.freedesktop.org, anshuman.gupta@intel.com,
badal.nilawar@intel.com, rodrigo.vivi@intel.com
Subject: Re: [PATCH] drm/xe/hwmon: Prevent unintended VRAM channel creation
Date: Wed, 11 Feb 2026 12:17:04 +0100 [thread overview]
Message-ID: <aYxlMOmslu34lfqD@black.igk.intel.com> (raw)
In-Reply-To: <20260206081655.2115439-1-karthik.poosa@intel.com>
On Fri, Feb 06, 2026 at 01:46:55PM +0530, Karthik Poosa wrote:
> Remove the unnecessary VRAM channel entry introduced in xe_hwmon_channel.
> Without this, adding any new hwmon channel causes extra VRAM channel
> to appear. This remained unnoticed earlier because VRAM was the
> final xe hwmon channel.
>
> v2: Use MAX_VRAM_CHANNELS with in_range() instead of
> CHANNEL_VRAM_N_MAX. (Raag)
>
> Signed-off-by: Karthik Poosa <karthik.poosa@intel.com>
> Fixes: 49a498338417 ("drm/xe/hwmon: Expose individual VRAM channel temperature")
Fixes tag usually goes first, but perhaps it can be re-ordered while
applying. In any case,
Reviewed-by: Raag Jadav <raag.jadav@intel.com>
> ---
> drivers/gpu/drm/xe/xe_hwmon.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_hwmon.c b/drivers/gpu/drm/xe/xe_hwmon.c
> index baf277955b33..0fd4d4f1014a 100644
> --- a/drivers/gpu/drm/xe/xe_hwmon.c
> +++ b/drivers/gpu/drm/xe/xe_hwmon.c
> @@ -48,7 +48,7 @@ enum xe_hwmon_channel {
> CHANNEL_MCTRL,
> CHANNEL_PCIE,
> CHANNEL_VRAM_N,
> - CHANNEL_VRAM_N_MAX = CHANNEL_VRAM_N + MAX_VRAM_CHANNELS,
> + CHANNEL_VRAM_N_MAX = CHANNEL_VRAM_N + MAX_VRAM_CHANNELS - 1,
> CHANNEL_MAX,
> };
>
> @@ -264,7 +264,7 @@ static struct xe_reg xe_hwmon_get_reg(struct xe_hwmon *hwmon, enum xe_hwmon_reg
> return BMG_PACKAGE_TEMPERATURE;
> else if (channel == CHANNEL_VRAM)
> return BMG_VRAM_TEMPERATURE;
> - else if (in_range(channel, CHANNEL_VRAM_N, CHANNEL_VRAM_N_MAX))
> + else if (in_range(channel, CHANNEL_VRAM_N, MAX_VRAM_CHANNELS))
> return BMG_VRAM_TEMPERATURE_N(channel - CHANNEL_VRAM_N);
> } else if (xe->info.platform == XE_DG2) {
> if (channel == CHANNEL_PKG)
> @@ -1427,7 +1427,7 @@ static int xe_hwmon_read_label(struct device *dev,
> *str = "mctrl";
> else if (channel == CHANNEL_PCIE)
> *str = "pcie";
> - else if (in_range(channel, CHANNEL_VRAM_N, CHANNEL_VRAM_N_MAX))
> + else if (in_range(channel, CHANNEL_VRAM_N, MAX_VRAM_CHANNELS))
> *str = hwmon->temp.vram_label[channel - CHANNEL_VRAM_N];
> return 0;
> case hwmon_power:
> --
> 2.25.1
>
next prev parent reply other threads:[~2026-02-11 11:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 8:16 [PATCH] drm/xe/hwmon: Prevent unintended VRAM channel creation Karthik Poosa
2026-02-06 8:17 ` ✓ CI.KUnit: success for drm/xe/hwmon: Prevent unintended VRAM channel creation (rev2) Patchwork
2026-02-06 8:55 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-07 10:25 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-11 11:17 ` Raag Jadav [this message]
2026-02-18 0:22 ` [PATCH] drm/xe/hwmon: Prevent unintended VRAM channel creation Rodrigo Vivi
-- strict thread matches above, loose matches on Subject: below --
2026-01-19 14:31 Karthik Poosa
2026-01-20 13:38 ` Raag Jadav
2026-02-06 7:29 ` Poosa, Karthik
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=aYxlMOmslu34lfqD@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=karthik.poosa@intel.com \
--cc=rodrigo.vivi@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