mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Jean Delvare <khali@linux-fr.org>
Cc: Rudolf Marek <r.marek@assembler.cz>, Ingo Molnar <mingo@elte.hu>,
	x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	LM Sensors <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] [PATCH-tip] x86: hwmon/k8temp.c Add support for  AMD 10H and 11H
Date: Mon, 25 May 2009 19:47:19 +0530	[thread overview]
Message-ID: <1243261039.3098.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20090525154501.3f251a23@hyperion.delvare>

Hello Jean,

On Mon, 2009-05-25 at 15:45 +0200, Jean Delvare wrote:
> Hi Jaswinder,
> 
> On Fri, 22 May 2009 15:00:48 +0530, Jaswinder Singh Rajput wrote:
> > Atleast something is better than nothing ;-)
> 
> Sorry but you are wrong here. When it comes to hardware monitoring (or
> monitoring in general), potentially wrong data is _worse_ than no data
> at all, unless you additionally carry the information that the data
> value may be wrong, and display it in a very visible manner. As our
> sysfs interface doesn't provide any way to pass reliability information
> to the reader (and I don't think it would make sense to add one), it is
> better to not export data that we know can't be trusted.
> 

As I said in my previous email that it seems problem is with few 10H
cpus and 11H are OK.

So better we will fix wrong information or suppress information for
those specific cpus.

On my 11H laptop monitoring seems very reliable. So in the worst case we
drop support for 10H.

Thanks,
--
JSR




      reply	other threads:[~2009-05-25 14:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22  8:04 Jaswinder Singh Rajput
2009-05-22  8:16 ` Rudolf Marek
2009-05-22  8:42   ` Jaswinder Singh Rajput
2009-05-22  9:30     ` Jaswinder Singh Rajput
2009-05-23 16:59       ` Rudolf Marek
2009-05-24 12:19         ` Jaswinder Singh Rajput
2009-05-26 12:10         ` Jaswinder Singh Rajput
2009-05-26 15:20           ` Rudolf Marek
2009-05-26 15:44             ` Jaswinder Singh Rajput
2009-05-28 11:57               ` Jaswinder Singh Rajput
2009-05-28 12:28                 ` [lm-sensors] " Jean Delvare
2009-05-28 14:13                   ` Jaswinder Singh Rajput
2009-05-28 14:49                     ` [stable] " Greg KH
2009-05-29  5:42                       ` Jaswinder Singh Rajput
2009-05-29  6:05                         ` Jean Delvare
2009-06-06 10:36               ` Jaswinder Singh Rajput
2009-06-20  7:56               ` [HWMON] x86: hwmon/k8temp.c Add support for AMD 11H Jaswinder Singh Rajput
2009-06-25 14:09                 ` Jaswinder Singh Rajput
2009-07-19  5:03                   ` Jaswinder Singh Rajput
2009-05-25 13:45       ` [lm-sensors] [PATCH-tip] x86: hwmon/k8temp.c Add support for AMD 10H and 11H Jean Delvare
2009-05-25 14:17         ` Jaswinder Singh Rajput [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=1243261039.3098.5.camel@localhost.localdomain \
    --to=jaswinder@kernel.org \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=mingo@elte.hu \
    --cc=r.marek@assembler.cz \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome