On Wed, 30 Apr 2008 02:11:14 +0200, Kasper Sandberg wrote:It's really only an offset, rather than scaling. The temperature reported by the Core and Core2 CPUs is a relative temperature. It tells how far you are from the maximum temperature the CPU can survive. The value is expressed in (relative) degrees C. Rudolf did his best to find out the (absolute) temperature each CPU model can survive (known as TJmax) so that the coretemp driver can provide an absolute temperature to user-space, as all other hardware monitoring drivers do. Our hope was to limit the confusion, but it seems we failed ;) Maybe it would be better if the driver was reporting the relative temperature value directly when we don't know the TJmax value for sure - but then all user-space tools would need to learn how to deal with this. It should, but there's no guarantee on desktop/server CPUs. It can be offset by 15°C if the driver's heuristic to determine TJmax for your CPU is incorrect. I guess the offset could even be different - after all the documentation we got from Intel was incomplete so we don't really know. -- Jean Delvare --
| Linus Torvalds | Linux 2.6.27-rc5 |
| Ingo Molnar | [announce] "kill the Big Kernel Lock (BKL)" tree |
| Christoph Lameter | Re: [RFC 00/15] x86_64: Optimize percpu accesses |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH iproute2] Re: HTB accuracy for high speed |
