All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jordan Crouse <jordan@cosmicpenguin.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH 1/2] k8temp warn about errata
Date: Mon, 10 Nov 2008 01:27:53 +0000	[thread overview]
Message-ID: <49178E19.9050301@cosmicpenguin.net> (raw)
In-Reply-To: <48E3F505.40401@assembler.cz>

Jean Delvare wrote:
> Hi Rudolf,
> 
> On Sun, 09 Nov 2008 20:56:54 +0100, Rudolf Marek wrote:
>> Thanks for the review. I'm attaching fixed version.
>>
>> Following patch adds warning about wrong CPU temperature readouts on all fam f
>> rev f revision of CPUs.
>>
>> Used switch statement, more code changes follows.
>>
>> Signed-off-by: Rudolf Marek <r.marek@assembler.cz>
> 
> I've applied it, thanks. Note that I added a "break" at the end of the
> case 0xf, otherwise it's an invitation to get things wrong in the next
> patch...
> 
>>> If all revision F and later CPUs are affected by the errata and the
>>> temperature reported is never correct, we should simply blacklist these
>>> CPUs. I guess this isn't the case, otherwise you'd have proposed that
>>> we do that long ago.
>> Yes.
>>
>>> If most but not all of these CPUs are affected, then it would make
>>> sense to disable them by default but give the user a chance to still
>>> enable them (using a module parameter.)
>> I tried hard to get this info from AMD. All versions are affected, but some may
>> be fixed/not tested.
>>
>>> If there are more revision F and later CPUs with working thermal
>>> diodes, and working ones can be told from non-working ones based on the
>>> exact revision, we could implement blacklisting and/or whitelisting
>>> base on the revision.
>> The errata is for all revs.
> 
> For what it's worth, Jordan Crouse seems to think that blacklisting on
> a per-revision basis may still work.

I think it can.  A much larger sample would probably need to be taken to 
be completely sure - but I hope that we'll find that the problem is 
deterministic enough for a blacklist.  I think we would agree that a 
blacklist would be the more user friendly solution.

Jordan


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2008-11-10  1:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 22:09 [lm-sensors] [PATCH 1/2] k8temp warn about errata Rudolf Marek
2008-10-25 12:43 ` Jean Delvare
2008-10-27  1:18 ` Jean-Marc Spaggiari
2008-11-09 19:56 ` Rudolf Marek
2008-11-09 20:47 ` Jean Delvare
2008-11-09 20:54 ` Jean Delvare
2008-11-10  1:27 ` Jordan Crouse [this message]
2008-11-10  9:38 ` Jean Delvare
2008-11-18  8:41 ` Andreas Herrmann
2008-11-18  8:55 ` Andreas Herrmann
2008-11-18  9:06 ` Jean Delvare
2008-11-18  9:25 ` Andreas Herrmann
2008-11-18 10:10 ` Andreas Herrmann
2008-11-18 10:40 ` Jean Delvare
2008-11-18 11:18 ` Andreas Herrmann
2008-11-18 11:26 ` Andreas Herrmann
2008-11-18 12:33 ` Jean Delvare
2008-11-18 12:57 ` Jean Delvare
2008-11-18 17:46 ` Jordan Crouse
2008-11-18 18:15 ` Jean Delvare

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=49178E19.9050301@cosmicpenguin.net \
    --to=jordan@cosmicpenguin.net \
    --cc=lm-sensors@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 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.