Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Ricardo Neri" <ricardo.neri-calderon@linux.intel.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v2] hwmon: (coretemp) Return -ENODATA for invalid temperature readings
Date: Tue, 06 Oct 2026 13:01:12 +0000	[thread overview]
Message-ID: <20261006130112.D691A1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261006-coretemp-enodata-v2-1-64e788acc7dc@linux.intel.com>

> IA32_THERM_STATUS and IA32_PACKAGE_THERM_STATUS have a valid bit, bit 31.
> The Intel SDM documents it only for the former, but the package register
> implements it too: x86_pkg_temp_thermal has required it since commit
> f1a18a105660 ("Thermal: CPU Package temperature thermal").
> 
> This driver checked the bit for both registers as well, until
> commit bf6ea084ebb5 ("hwmon: (coretemp) Do not return -EAGAIN for low
> temperatures") made it ignore the bit because some CPUs clear it while
> the temperature is too low to be measured. Since then, temp%d_input
> reports such a reading as a real temperature. Userspace cannot tell it
> apart from a genuinely low one.
> 
> Fail the read with -ENODATA while the CPU reports the reading as invalid.
> On a CPU that clears the bit, reading temp%d_input now fails where it
> used to return a low value. sensors(1) shows N/A in its place.
> 
> Suggested-by: Guenter Roeck <linux@roeck-us.net>
> Link: https://lore.kernel.org/all/46f9f319-de71-412f-a424-6cb801478456@roeck-us.net/
> 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/20261006-coretemp-enodata-v2-1-64e788acc7dc@linux.intel.com?part=1


      reply	other threads:[~2026-10-06 13:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06 13:04 [PATCH v2] hwmon: (coretemp) Return -ENODATA for invalid temperature readings Ricardo Neri
2026-10-06 13:01 ` sashiko-bot [this message]

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=20261006130112.D691A1F000FF@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