From: sashiko-bot@kernel.org
To: "Ricardo Neri" <ricardo.neri-calderon@linux.intel.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 3/3] hwmon: (coretemp) Add temp%d_fault sysfs attribute
Date: Fri, 25 Sep 2026 02:31:15 +0000 [thread overview]
Message-ID: <20260925023116.0C6971F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260924-coretemp-temp-fault-v1-3-1884f0ff97d5@linux.intel.com>
> The temp%d_input sysfs attribute reports the CPU core temperature
> regardless of the valid bit (bit 31) in IA32_[PACKAGE]_THERM_STATUS.
> Commit bf6ea084ebb5 ("hwmon: (coretemp) Do not return -EAGAIN for low
> temperatures") established this behavior after observing that some Intel
> CPUs do not set the valid bit while the temperature is too low to be
> measured. The value reported is of more use than an error. Changing this is
> not an option: the interface is long-established and userspace relies on
> it never failing.
>
> Userspace, however, cannot distinguish a genuinely low temperature from
> one the CPU could not measure. Until that commit it could: reading
> temp%d_input returned -EAGAIN. That signal was removed and nothing
> replaced it. Report the inverse of the valid bit through the standard hwmon
> temp%d_fault attribute. Its documented meaning is that the measurement
> for that channel should not be trusted. Tools built on libsensors consume
> the standard attribute.
>
> temp%d_input continues to ignore the valid bit. A new update_temp() helper
> refreshes the cached temperature and its fault state together, so both
> attributes are served from the same reading of the status register.
>
> Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260924-coretemp-temp-fault-v1-0-1884f0ff97d5@linux.intel.com?part=3
next prev parent reply other threads:[~2026-09-25 2:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 2:33 [PATCH 0/3] hwmon: (coretemp) Report unreliable temperature readings Ricardo Neri
2026-09-25 2:33 ` [PATCH 1/3] hwmon: (coretemp) Refresh the temperature on the first read Ricardo Neri
2026-09-25 2:32 ` sashiko-bot
2026-09-25 14:03 ` Guenter Roeck
2026-09-25 2:33 ` [PATCH 2/3] hwmon: (coretemp) Read TjMax only when refreshing the temperature Ricardo Neri
2026-09-25 2:29 ` sashiko-bot
2026-09-25 14:04 ` Guenter Roeck
2026-09-25 2:33 ` [PATCH 3/3] hwmon: (coretemp) Add temp%d_fault sysfs attribute Ricardo Neri
2026-09-25 2:31 ` sashiko-bot [this message]
2026-09-25 2:37 ` [PATCH 0/3] hwmon: (coretemp) Report unreliable temperature readings Guenter Roeck
2026-09-25 18:21 ` Ricardo Neri
2026-09-25 21:23 ` Guenter Roeck
2026-09-26 3:58 ` Ricardo Neri
2026-09-28 11:01 ` Guenter Roeck
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=20260925023116.0C6971F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=ricardo.neri-calderon@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox