All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Jean Delvare <khali@linux-fr.org>
Cc: Kasper Sandberg <lkml@metanurb.dk>,
	Rudolf Marek <r.marek@assembler.cz>,
	Maxim Levitsky <maximlevitsky@gmail.com>,
	trenn@suse.de, Len Brown <lenb@kernel.org>,
	Matthew <jackdachef@gmail.com>,
	linux-acpi@vger.kernel.org, torvalds@linux-foundation.org,
	linux-kernel@vger.kernel.org, "Zhang, Rui" <rui.zhang@intel.com>
Subject: Re: Linux 2.6.25 (coretemp reads high temperatures)
Date: Wed, 30 Apr 2008 11:51:10 -0300	[thread overview]
Message-ID: <20080430145110.GC3543@khazad-dum.debian.net> (raw)
In-Reply-To: <20080430082005.4b76186f@hyperion.delvare>

On Wed, 30 Apr 2008, Jean Delvare wrote:
> On Wed, 30 Apr 2008 02:11:14 +0200, Kasper Sandberg wrote:
> > On Wed, 2008-04-30 at 00:14 +0200, Rudolf Marek wrote:
> > > Well again, I tried hard at Intel and I really could not get any info on some
> > > calibration bit. The temperature is non-physical on arbitrary scale. I changed
> > > that so for some people it jumped to 100C, for some it remained.
> > 
> > So, im confused.. The reason for this is that the internal sensor is
> > operating on some sort of weird scale, and thus when you interpolate it
> > into "your" scale, it doesent quite come out in the actual degrees
> > celcius the cpu temperature really is?
> 
> 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.

Ah, please ignore my email about ITUs (Intel thermal units), then.  The
above means 1ITU=1°C, but their zeros are at different places.

> 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.

Actually, just libsensors would, and the local admin can adjust it at
will using the config file.

Nobody in userspace should be reading hwmon sysfs directly without the
use of libsensors.  If they are, it is their bug, and it is unsupported
AFAIK.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Jean Delvare <khali@linux-fr.org>
Cc: Kasper Sandberg <lkml@metanurb.dk>,
	Rudolf Marek <r.marek@assembler.cz>,
	Maxim Levitsky <maximlevitsky@gmail.com>,
	trenn@suse.de, Len Brown <lenb@kernel.org>,
	Matthew <jackdachef@gmail.com>,
	linux-acpi@vger.kernel.org, torvalds@linux-foundation.org,
	linux-kernel@vger.kernel.org, "Zhang, Rui" <rui.zhang@intel.com>
Subject: Re: Linux 2.6.25 (coretemp reads high temperatures)
Date: Wed, 30 Apr 2008 11:51:10 -0300	[thread overview]
Message-ID: <20080430145110.GC3543@khazad-dum.debian.net> (raw)
In-Reply-To: <20080430082005.4b76186f@hyperion.delvare>

On Wed, 30 Apr 2008, Jean Delvare wrote:
> On Wed, 30 Apr 2008 02:11:14 +0200, Kasper Sandberg wrote:
> > On Wed, 2008-04-30 at 00:14 +0200, Rudolf Marek wrote:
> > > Well again, I tried hard at Intel and I really could not get any info on some
> > > calibration bit. The temperature is non-physical on arbitrary scale. I changed
> > > that so for some people it jumped to 100C, for some it remained.
> > 
> > So, im confused.. The reason for this is that the internal sensor is
> > operating on some sort of weird scale, and thus when you interpolate it
> > into "your" scale, it doesent quite come out in the actual degrees
> > celcius the cpu temperature really is?
> 
> 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.

Ah, please ignore my email about ITUs (Intel thermal units), then.  The
above means 1ITU=1°C, but their zeros are at different places.

> 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.

Actually, just libsensors would, and the local admin can adjust it at
will using the config file.

Nobody in userspace should be reading hwmon sysfs directly without the
use of libsensors.  If they are, it is their bug, and it is unsupported
AFAIK.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2008-04-30 14:51 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18 15:37 Linux 2.6.25 Matthew
2008-04-18 15:43 ` Linus Torvalds
2008-04-18 16:02   ` Matthew
2008-04-18 19:38   ` Cyrill Gorcunov
2008-04-18 20:03     ` Cyrill Gorcunov
2008-04-19  3:05       ` Rene Herman
2008-04-19  3:20         ` Rene Herman
2008-04-19  6:17           ` Cyrill Gorcunov
2008-04-19 10:18             ` Matthew
2008-04-19 10:22               ` Matthew
2008-04-20 12:02                 ` Matthew
2008-04-24  3:36                   ` Len Brown
2008-04-18 16:24 ` Gene Heskett
2008-04-18 16:27 ` Gene Heskett
2008-04-18 19:18 ` Bart Van Assche
2008-04-18 20:24   ` Jiri Slaby
2008-04-18 20:50     ` [lm-sensors] " Rudolf Marek
2008-04-18 20:50       ` Rudolf Marek
2008-04-19  1:51 ` Linux 2.6.25 (coretemp reads high temperatures) Len Brown
2008-04-21 16:10   ` Thomas Bächler
2008-04-21 16:28     ` Matthew
2008-04-21 17:07       ` Fwd: " Matthew
2008-04-22  9:26         ` Matthew
2008-04-23  8:43   ` Maxim Levitsky
2008-04-23  8:43     ` Maxim Levitsky
2008-04-28 18:19     ` Kasper Sandberg
2008-04-28 18:19       ` Kasper Sandberg
2008-04-29 13:07       ` Thomas Renninger
2008-04-29 15:08         ` Jean Delvare
2008-04-29 22:14           ` Rudolf Marek
2008-04-29 22:58             ` Matthew
2008-04-29 22:58               ` Matthew
2008-04-30  6:10               ` Jean Delvare
2008-04-30  6:10                 ` Jean Delvare
2008-04-30 14:46                 ` Henrique de Moraes Holschuh
2008-04-30 14:46                   ` Henrique de Moraes Holschuh
2008-04-30 14:50                   ` Rudolf Marek
2008-04-30 14:50                     ` Rudolf Marek
2008-04-30 15:18                     ` Jean Delvare
2008-04-30 15:18                       ` Jean Delvare
2008-05-02 20:35                   ` Pavel Machek
2008-05-02 20:35                     ` Pavel Machek
2008-04-30  0:11             ` Kasper Sandberg
2008-04-30  0:11               ` Kasper Sandberg
2008-04-30  6:20               ` Jean Delvare
2008-04-30  6:20                 ` Jean Delvare
2008-04-30 14:51                 ` Henrique de Moraes Holschuh [this message]
2008-04-30 14:51                   ` Henrique de Moraes Holschuh
2008-04-30 15:28                   ` Jean Delvare
2008-04-30 15:28                     ` Jean Delvare
2008-05-02 20:36                   ` Pavel Machek
2008-05-02 20:36                     ` Pavel Machek
2008-05-04 17:42                     ` Henrique de Moraes Holschuh
2008-05-05 13:45                       ` Pavel Machek
2008-05-02 20:35             ` Pavel Machek

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=20080430145110.GC3543@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=jackdachef@gmail.com \
    --cc=khali@linux-fr.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@metanurb.dk \
    --cc=maximlevitsky@gmail.com \
    --cc=r.marek@assembler.cz \
    --cc=rui.zhang@intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=trenn@suse.de \
    /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.