From: "Poosa, Karthik" <karthik.poosa@intel.com>
To: Raag Jadav <raag.jadav@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: Fri, 6 Feb 2026 12:59:33 +0530 [thread overview]
Message-ID: <87b81701-57a5-4e12-9115-2a69b9832185@intel.com> (raw)
In-Reply-To: <aW-FTFpA7cvJOoMa@black.igk.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1783 bytes --]
2
On 20-01-2026 19:08, Raag Jadav wrote:
> On Mon, Jan 19, 2026 at 08:01:38PM +0530, Karthik Poosa wrote:
>> Remove the unnecessary VRAM channel entry introduced in
>> xe_hwmon_channel. Without this, adding any new hwmon channel
>> causes an extra VRAM channel to appear. This remained unnoticed
>> earlier because VRAM was the final xe hwmon channel.
>>
>> Signed-off-by: Karthik Poosa<karthik.poosa@intel.com>
>> Fixes: 49a498338417 ("drm/xe/hwmon: Expose individual VRAM channel temperature")
>> ---
>> drivers/gpu/drm/xe/xe_hwmon.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_hwmon.c b/drivers/gpu/drm/xe/xe_hwmon.c
>> index baf277955b33..f614f1308dec 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,
> Can you also check in_range() logic and investigate how channel id greater
> than CHANNEL_VRAM_N_MAX (for example 23) is delt with?
>
> Raag
Hi Raag,
We are not seeing new channels with in_range() + CHANNEL_VRAM_N_MAX as
1. hwmon_info[] has defined only CHANNEL_VRAM_N_MAX channels,
2. CHANNEL_VRAM_N_MAX is the max channel supported in xe_hwmon.c
Checked in_range implementation also, you are right, using
|MAX_VRAM_CHANNELS| with |in_range|() is correct, |as it |requires a
start value and length.
Using |CHANNEL_VRAM_N_MAX| instead would pass offset which also includes
extra offsets from CHANNEL_CARD to CHANNEL_PCIe.
I will use MAX_VRAM_CHANNELS with in_range in the next revision.
>
>> CHANNEL_MAX,
>> };
>>
>> --
>> 2.25.1
>>
[-- Attachment #2: Type: text/html, Size: 4331 bytes --]
next prev parent reply other threads:[~2026-02-06 7:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 14:31 [PATCH] drm/xe/hwmon: Prevent unintended VRAM channel creation Karthik Poosa
2026-01-20 13:38 ` Raag Jadav
2026-02-06 7:29 ` Poosa, Karthik [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-06 8:16 Karthik Poosa
2026-02-11 11:17 ` Raag Jadav
2026-02-18 0:22 ` Rodrigo Vivi
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=87b81701-57a5-4e12-9115-2a69b9832185@intel.com \
--to=karthik.poosa@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=raag.jadav@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