All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Herrmann <andreas.herrmann3@amd.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH 1/4] hwmon: (k8temp) adapt cpuid handling,
Date: Wed, 10 Dec 2008 10:30:15 +0000	[thread overview]
Message-ID: <20081210103015.GL19144@alberich.amd.com> (raw)
In-Reply-To: <20081205174612.GB5581@alberich.amd.com>

On Wed, Dec 10, 2008 at 11:03:33AM +0100, Andreas Herrmann wrote:
> On Tue, Dec 09, 2008 at 11:12:39PM +0100, Rudolf Marek wrote:
> > Please tell me why it is not necessary or why you changed that ;)

To be more specific.

There are following CPUID checks necessary in k8temp:

>= K8 RevC

to check for support of temperature reporting at all.

>= RevF

to check for erratum #141

>= RevG (desktop)

to check for temperature skew

(In the future we might have additional checks for
family 0x10 >= RevC to check for erratum 319.)

This devides K8 CPUs into 4 classes (and family 10h CPUs into
2 classes).

Now it is important to notice that (by chance) you can't combine
processors of different classes in a mixed silicon setup.
See the relevant CPU revision guides for those CPUs.
E.g., combining RevC with RevF is not supported.

Thus it suffices to check CPUID of boot CPU.
We don't need to care about unsupported processor combinations.


Regards,
Andreas



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

  parent reply	other threads:[~2008-12-10 10:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 17:46 [lm-sensors] [PATCH 1/4] hwmon: (k8temp) adapt cpuid handling, Andreas Herrmann
2008-12-09 22:12 ` Rudolf Marek
2008-12-10 10:03 ` Andreas Herrmann
2008-12-10 10:30 ` Andreas Herrmann [this message]
2008-12-15 19:43 ` Rudolf Marek
2008-12-15 19:46 ` Rudolf Marek

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=20081210103015.GL19144@alberich.amd.com \
    --to=andreas.herrmann3@amd.com \
    --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.