From: "Winiarska, Iwona" <iwona.winiarska@intel.com>
To: "linux@roeck-us.net" <linux@roeck-us.net>,
"jae.hyun.yoo@linux.intel.com" <jae.hyun.yoo@linux.intel.com>,
"Rudolph, Patrick" <patrick.rudolph@9elements.com>,
"pierre-louis.bossart@linux.dev" <pierre-louis.bossart@linux.dev>,
"Solanki, Naresh" <naresh.solanki@9elements.com>,
"fercerpav@gmail.com" <fercerpav@gmail.com>,
"jdelvare@suse.com" <jdelvare@suse.com>
Cc: "fr0st61te@gmail.com" <fr0st61te@gmail.com>,
"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"joel@jms.id.au" <joel@jms.id.au>
Subject: Re: [PATCH] hwmon: (peci/dimmtemp) Do not provide fake thresholds data
Date: Mon, 27 Jan 2025 16:40:52 +0000 [thread overview]
Message-ID: <71b63aa1646af4ae30b59f6d70f3daaeb983b6f8.camel@intel.com> (raw)
In-Reply-To: <20250123122003.6010-1-fercerpav@gmail.com>
On Thu, 2025-01-23 at 15:20 +0300, Paul Fertser wrote:
> When an Icelake or Sapphire Rapids CPU isn't providing the maximum and
> critical thresholds for particular DIMM the driver should return an
> error to the userspace instead of giving it stale (best case) or wrong
> (the structure contains all zeros after kzalloc() call) data.
>
> The issue can be reproduced by binding the peci driver while the host is
> fully booted and idle, this makes PECI interaction unreliable enough.
>
> Fixes: 73bc1b885dae ("hwmon: peci: Add dimmtemp driver")
> Fixes: 621995b6d795 ("hwmon: (peci/dimmtemp) Add Sapphire Rapids support")
> Cc: stable@vger.kernel.org
> Signed-off-by: Paul Fertser <fercerpav@gmail.com>
Hi!
Thank you for the patch.
Did you have a chance to test it with OpenBMC dbus-sensors?
In general, the change looks okay to me, but since it modifies the behavior
(applications will need to handle this, and returning an error will happen more
often) we need to confirm that it does not cause any regressions for userspace.
Once we are able to confirm that:
Reviewed-by: Iwona Winiarska <iwona.winiarska@intel.com>
Thanks
-Iwona
> ---
> drivers/hwmon/peci/dimmtemp.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/hwmon/peci/dimmtemp.c b/drivers/hwmon/peci/dimmtemp.c
> index d6762259dd69..fbe82d9852e0 100644
> --- a/drivers/hwmon/peci/dimmtemp.c
> +++ b/drivers/hwmon/peci/dimmtemp.c
> @@ -127,8 +127,6 @@ static int update_thresholds(struct peci_dimmtemp *priv,
> int dimm_no)
> return 0;
>
> ret = priv->gen_info->read_thresholds(priv, dimm_order, chan_rank,
> &data);
> - if (ret == -ENODATA) /* Use default or previous value */
> - return 0;
> if (ret)
> return ret;
>
> @@ -509,11 +507,11 @@ read_thresholds_icx(struct peci_dimmtemp *priv, int
> dimm_order, int chan_rank, u
>
> ret = peci_ep_pci_local_read(priv->peci_dev, 0, 13, 0, 2, 0xd4,
> ®_val);
> if (ret || !(reg_val & BIT(31)))
> - return -ENODATA; /* Use default or previous value */
> + return -ENODATA;
>
> ret = peci_ep_pci_local_read(priv->peci_dev, 0, 13, 0, 2, 0xd0,
> ®_val);
> if (ret)
> - return -ENODATA; /* Use default or previous value */
> + return -ENODATA;
>
> /*
> * Device 26, Offset 224e0: IMC 0 channel 0 -> rank 0
> @@ -546,11 +544,11 @@ read_thresholds_spr(struct peci_dimmtemp *priv, int
> dimm_order, int chan_rank, u
>
> ret = peci_ep_pci_local_read(priv->peci_dev, 0, 30, 0, 2, 0xd4,
> ®_val);
> if (ret || !(reg_val & BIT(31)))
> - return -ENODATA; /* Use default or previous value */
> + return -ENODATA;
>
> ret = peci_ep_pci_local_read(priv->peci_dev, 0, 30, 0, 2, 0xd0,
> ®_val);
> if (ret)
> - return -ENODATA; /* Use default or previous value */
> + return -ENODATA;
>
> /*
> * Device 26, Offset 219a8: IMC 0 channel 0 -> rank 0
next prev parent reply other threads:[~2025-01-27 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 12:20 [PATCH] hwmon: (peci/dimmtemp) Do not provide fake thresholds data Paul Fertser
2025-01-27 16:40 ` Winiarska, Iwona [this message]
2025-01-27 17:29 ` Guenter Roeck
2025-01-27 18:30 ` Paul Fertser
2025-01-27 18:39 ` Guenter Roeck
2025-01-27 19:10 ` Paul Fertser
2025-01-28 3:34 ` Guenter Roeck
2025-01-27 18:54 ` Paul Fertser
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=71b63aa1646af4ae30b59f6d70f3daaeb983b6f8.camel@intel.com \
--to=iwona.winiarska@intel.com \
--cc=fercerpav@gmail.com \
--cc=fr0st61te@gmail.com \
--cc=jae.hyun.yoo@linux.intel.com \
--cc=jdelvare@suse.com \
--cc=joel@jms.id.au \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=naresh.solanki@9elements.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick.rudolph@9elements.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=stable@vger.kernel.org \
/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