From: Jean Delvare <khali@linux-fr.org>
To: Huaxu Wan <huaxu.wan@linux.intel.com>
Cc: Robert Hancock <hancockrwd@gmail.com>,
Yuhong Bao <yuhongbao_386@hotmail.com>,
lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org,
yong.y.wang@linux.intel.com
Subject: Re: [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom
Date: Mon, 18 Jan 2010 08:07:11 +0000 [thread overview]
Message-ID: <20100118090711.5be2f70c@hyperion.delvare> (raw)
In-Reply-To: <20100118072138.GA25107@owl>
On Mon, 18 Jan 2010 15:21:38 +0800, Huaxu Wan wrote:
> On 21:05 Sun 17 Jan, Jean Delvare wrote:
> > Anyway, how difficult would it be to set TjMax based on the CPUID? I
> > presume that the Intel Atom 400 and 500 series have their own CPUID
> > value, haven't they? This would seem even easier that checking for a
> > PCI device.
>
> Actually, all the Atom processors share the same CPUID(0x1C) and the
> worse is not all of them has the same TjMax. That's a big problem.
0x1C is the product value. The stepping value could be different. There
could also be other identification methods based on cpuid() or rdmsr()
commands. This is done quite frequently to identify specific CPU models.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
WARNING: multiple messages have this Message-ID (diff)
From: Jean Delvare <khali@linux-fr.org>
To: Huaxu Wan <huaxu.wan@linux.intel.com>
Cc: Robert Hancock <hancockrwd@gmail.com>,
Yuhong Bao <yuhongbao_386@hotmail.com>,
lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org,
yong.y.wang@linux.intel.com
Subject: Re: [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs
Date: Mon, 18 Jan 2010 09:07:11 +0100 [thread overview]
Message-ID: <20100118090711.5be2f70c@hyperion.delvare> (raw)
In-Reply-To: <20100118072138.GA25107@owl>
On Mon, 18 Jan 2010 15:21:38 +0800, Huaxu Wan wrote:
> On 21:05 Sun 17 Jan, Jean Delvare wrote:
> > Anyway, how difficult would it be to set TjMax based on the CPUID? I
> > presume that the Intel Atom 400 and 500 series have their own CPUID
> > value, haven't they? This would seem even easier that checking for a
> > PCI device.
>
> Actually, all the Atom processors share the same CPUID(0x1C) and the
> worse is not all of them has the same TjMax. That's a big problem.
0x1C is the product value. The stepping value could be different. There
could also be other identification methods based on cpuid() or rdmsr()
commands. This is done quite frequently to identify specific CPU models.
--
Jean Delvare
next prev parent reply other threads:[~2010-01-18 8:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 7:31 [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Yong Wang
2010-01-06 15:08 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom Jean Delvare
2010-01-06 15:08 ` [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Jean Delvare
2010-01-10 19:06 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom Jean Delvare
2010-01-10 19:06 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Jean Delvare
2010-01-11 6:20 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Yong Wang
2010-01-11 6:20 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Yong Wang
2010-01-16 2:02 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom Yuhong Bao
2010-01-16 2:02 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Yuhong Bao
2010-01-17 15:15 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom Jean Delvare
2010-01-17 15:15 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Jean Delvare
2010-01-17 19:29 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom Robert Hancock
2010-01-17 19:29 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Robert Hancock
2010-01-17 20:05 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom Jean Delvare
2010-01-17 20:05 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Jean Delvare
2010-01-18 6:58 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Yong Wang
2010-01-18 6:58 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Yong Wang
2010-01-18 8:14 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom Jean Delvare
2010-01-18 8:14 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Jean Delvare
2010-01-18 8:27 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Yong Wang
2010-01-18 8:27 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Yong Wang
2010-01-18 7:21 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom Huaxu Wan
2010-01-18 7:21 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Huaxu Wan
2010-01-18 8:07 ` Jean Delvare [this message]
2010-01-18 8:07 ` 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=20100118090711.5be2f70c@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=hancockrwd@gmail.com \
--cc=huaxu.wan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=yong.y.wang@linux.intel.com \
--cc=yuhongbao_386@hotmail.com \
/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.