From: "Poosa, Karthik" <karthik.poosa@intel.com>
To: <sashiko-reviews@lists.linux.dev>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v2 5/5] drm/xe/hwmon: Disable memory controller and PCIe temperatures on CRI
Date: Thu, 3 Sep 2026 11:41:40 +0530 [thread overview]
Message-ID: <4321ffb7-e31a-4659-850b-27da377c30c3@intel.com> (raw)
In-Reply-To: <20260902180715.508DD1F000E9@smtp.kernel.org>
On 02-09-2026 23:37, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] The patch uses an enum ordering check that inadvertently disables memory controller and PCIe temperatures on Nova Lake P, splitting the Novalake platform family.
> --
>
> commit 91ec5832293666790affd1f3a6202739f54f4e49
> Author: Karthik Poosa <karthik.poosa@intel.com>
>
> drm/xe/hwmon: Disable memory controller and PCIe temperatures on CRI
>
> Temporarily disable memory controller and PCIe temperature reporting on
> CRI platforms. The definitions and interpretation of these temperature
> sources are not yet sufficiently clear, which may result in inaccurate
> reporting.
>
>> diff --git a/drivers/gpu/drm/xe/xe_hwmon.c b/drivers/gpu/drm/xe/xe_hwmon.c
>> index c2b8d4c79783a..5b2cef292ffcc 100644
>> --- a/drivers/gpu/drm/xe/xe_hwmon.c
>> +++ b/drivers/gpu/drm/xe/xe_hwmon.c
>> @@ -1061,8 +1061,14 @@ static bool is_temp_available(struct xe_hwmon *hwmon, int channel)
>>
>> return true;
>> case CHANNEL_MCTRL:
>> + if (hwmon->xe->info.platform >= XE_CRESCENTISLAND)
>> + return false;
>> +
>> return hwmon->temp.count && !get_mc_temp(hwmon, NULL);
>> case CHANNEL_PCIE:
>> + if (hwmon->xe->info.platform >= XE_CRESCENTISLAND)
>> + return false;
>> +
> [Severity: Medium]
> Does this check inadvertently affect Nova Lake P?
>
> Looking at the enum definition in xe_platform_types.h, XE_NOVALAKE_P is
> defined after XE_CRESCENTISLAND, while XE_NOVALAKE_S is defined before it:
>
> XE_NOVALAKE_S,
> XE_CRESCENTISLAND,
> XE_NOVALAKE_P,
>
> Using the >= operator will disable memory controller and PCIe temperatures on
> Nova Lake P, while they remain enabled for Nova Lake S. This seems to
> contradict the commit message which states this disables temperatures on CRI
> platforms.
>
> Should these checks use == XE_CRESCENTISLAND instead to avoid splitting the
> Novalake family?
HWMON is only supported on discrete GPUs. You can see here,
int xe_hwmon_register(struct xe_device *xe)
{
struct device *dev = xe->drm.dev;
struct xe_hwmon *hwmon;
int ret;
/* hwmon is available only for dGfx */
if (!IS_DGFX(xe))
return 0;
....
}
So for both Novalake platforms the function itself wont be called.
>
>> return hwmon->temp.count && !get_pcie_temp(hwmon, NULL);
>> default:
>> return false;
next prev parent reply other threads:[~2026-09-03 6:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 17:55 [PATCH v2 0/5] drm/xe/hwmon: Update hwmon thermal mailbox handling Karthik Poosa
2026-09-02 17:55 ` [PATCH v2 1/5] drm/xe/hwmon: Detect unavailable temperature sensors Karthik Poosa
2026-09-02 17:55 ` [PATCH v2 2/5] drm/xe/hwmon: Use VRAM temperature sensor count from thermal config on CRI Karthik Poosa
2026-09-02 18:10 ` sashiko-bot
2026-09-10 10:42 ` Poosa, Karthik
2026-09-02 18:43 ` Rodrigo Vivi
2026-09-10 11:33 ` Poosa, Karthik
2026-09-02 17:55 ` [PATCH v2 3/5] drm/xe/hwmon: Correct group selection for memory controller temperature Karthik Poosa
2026-09-02 18:17 ` sashiko-bot
2026-09-10 17:00 ` Poosa, Karthik
2026-09-02 17:55 ` [PATCH v2 4/5] drm/xe/hwmon: Decode CRI temperature registers as IEEE-754 Karthik Poosa
2026-09-02 18:08 ` sashiko-bot
2026-09-10 17:05 ` Poosa, Karthik
2026-09-02 17:55 ` [PATCH v2 5/5] drm/xe/hwmon: Disable memory controller and PCIe temperatures on CRI Karthik Poosa
2026-09-02 18:07 ` sashiko-bot
2026-09-03 6:11 ` Poosa, Karthik [this message]
2026-09-02 18:28 ` ✓ CI.KUnit: success for drm/xe/hwmon: Update hwmon thermal mailbox handling (rev2) Patchwork
2026-09-02 19:22 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-09-03 9:37 ` ✗ Xe.CI.FULL: " 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=4321ffb7-e31a-4659-850b-27da377c30c3@intel.com \
--to=karthik.poosa@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.