mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Guenter Roeck <guenter.roeck@ericsson.com>
Cc: Jan Beulich <JBeulich@novell.com>,
	"r.marek@assembler.cz" <r.marek@assembler.cz>,
	"fenghua.yu@intel.com" <fenghua.yu@intel.com>,
	"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: x86/hwmon: conditionalize coretemp's dependency on PCI
Date: Tue, 28 Sep 2010 17:20:23 +0200	[thread overview]
Message-ID: <20100928172023.75607337@endymion.delvare> (raw)
In-Reply-To: <20100928120000.GA7139@ericsson.com>

On Tue, 28 Sep 2010 05:00:00 -0700, Guenter Roeck wrote:
> On Tue, Sep 28, 2010 at 03:17:59AM -0400, Jean Delvare wrote:
> > Do you mean it is strange from a technical perspective, or do you have
> > evidences that it doesn't work properly? This trick come from Intel
> > themselves, I would guess they know their business.
>
> From a technical perspective. Hard to see what a PCI bridge ID has to do with Tjmax.

I agree. If you search the archives, you'll see I emitted exactly the
same complaint back then.

> > (...)
> > Higher or lower doesn't make a difference. As long as the coretemp
> > driver doesn't properly report the temperature values as being
> > relative, users don't expect the value to change depending on the
> > kernel version or configuration options. We have had dozens of user
> > reports because of this.
> > 
> You are right, functionality would change if someone runs a kernel with PCI undefined 
> on the specific systems which do use the PCI bridge ID to determine Tjmax. So 
> if there are no other options, maybe the big fat warning in that case would make sense.
> I would definitely prefer that over disabling coretemp entirely just because it _might_
> possibly report a wrong Tjmax (which it doees anyway for many CPUs).

I fully agree.

-- 
Jean Delvare

      reply	other threads:[~2010-09-28 15:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13 10:26 [PATCH] " Jan Beulich
2010-09-24 18:55 ` Guenter Roeck
2010-09-27  7:08   ` Jan Beulich
2010-09-27 12:16     ` Guenter Roeck
2010-09-27 12:46       ` Jan Beulich
2010-09-27 13:02         ` Guenter Roeck
2010-09-27 15:23           ` Jan Beulich
2010-09-28  7:17           ` Jean Delvare
2010-09-28 12:00             ` Guenter Roeck
2010-09-28 15:20               ` Jean Delvare [this message]

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=20100928172023.75607337@endymion.delvare \
    --to=khali@linux-fr.org \
    --cc=JBeulich@novell.com \
    --cc=fenghua.yu@intel.com \
    --cc=guenter.roeck@ericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=r.marek@assembler.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®