From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: Fenghua Yu <fenghua.yu@intel.com>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@linux.intel.com>,
"Brown, Len" <len.brown@intel.com>,
Chen Gong <gong.chen@linux.intel.com>,
"Wan, Huaxu" <huaxu.wan@intel.com>,
lkml <linux-kernel@vger.kernel.org>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] [PATCH 5/5] Package Level Thermal Control and
Date: Thu, 19 Aug 2010 16:27:19 +0000 [thread overview]
Message-ID: <20100819162719.GB4160@ericsson.com> (raw)
In-Reply-To: <20100819174632.239aed93@hyperion.delvare>
On Thu, Aug 19, 2010 at 11:46:32AM -0400, Jean Delvare wrote:
> Hi Fenghua, Guenter,
>
> Sorry for joining the discussion a little late, I was on vacation when
> it happened. I'll comment now, it's probably "too late" as the patch
> set was merged meanwhile, but still...
>
There was no discussion at all, unfortunately.
> On Thu, 22 Jul 2010 14:21:11 -0700, Fenghua Yu wrote:
> > On Thu, Jul 22, 2010 at 11:58:14AM -0700, Guenter Roeck wrote:
> > > You use the argument that there may be other package level sensors in the future.
> > > Are there any plans for this, or is this just a theory ?
> >
> > Not just a theory. Sandy Bridge already implements other package level sensors.
> > If really need to know exactly which sensors are implemented, we might go
> > through a channel before releasing the info.
> >
> > > Next question is how to handle future sensor types. One hwmon instance per sensor,
> > > additional sensors in this driver, or even a new driver ?
> >
> > Currently package level thermal just reports the maximum temperature across
> > the package. Which sensor is reporting the highest temperature is not exposed.
>
> So this isn't a real physical sensor, but more of a meta-sensor? If
> this is a case, then we don't need support for this at all. User-space
> can compute a maximum by itself, we don't need a dedicated kernel
> driver for that.
>
> > > We had was a separate discussion if the coretemp driver should be redesigned
> > > to one instance per CPU. The package sensor would fit into that model,
> > > since you would have
> > >
> > > coretemp-isa-0000
> > > Core0
> > > Core1
> > > ...
> > > CoreN
> > > Package
> > >
> > > coretemp-isa-0001
> > > Core0
> > > Core1
> > > ...
> > > CoreM
> > > Package
> > >
> > > I personally would prefer that approach. It would avoid ambiguity associating Package X
> > > with specific cores, and it would also easily expand to additional non-core future sensors.
>
> For the records, I totally support this approach. I want the coretemp
> driver to be updated to present a single hwmon device per CPU, no
> matter what happens to the "package temperature".
>
I might spend some time rewriting the coretemp driver as described above,
unless someone else picks it up, and unless there is opposition.
Obviously, that won't include the package sensor since there is now
a separate driver for it.
Guenter
_______________________________________________
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: Guenter Roeck <guenter.roeck@ericsson.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: Fenghua Yu <fenghua.yu@intel.com>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@linux.intel.com>,
"Brown, Len" <len.brown@intel.com>,
Chen Gong <gong.chen@linux.intel.com>,
"Wan, Huaxu" <huaxu.wan@intel.com>,
lkml <linux-kernel@vger.kernel.org>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>
Subject: Re: [PATCH 5/5] Package Level Thermal Control and Power Limit Notification: pkgtemp doc
Date: Thu, 19 Aug 2010 09:27:19 -0700 [thread overview]
Message-ID: <20100819162719.GB4160@ericsson.com> (raw)
In-Reply-To: <20100819174632.239aed93@hyperion.delvare>
On Thu, Aug 19, 2010 at 11:46:32AM -0400, Jean Delvare wrote:
> Hi Fenghua, Guenter,
>
> Sorry for joining the discussion a little late, I was on vacation when
> it happened. I'll comment now, it's probably "too late" as the patch
> set was merged meanwhile, but still...
>
There was no discussion at all, unfortunately.
> On Thu, 22 Jul 2010 14:21:11 -0700, Fenghua Yu wrote:
> > On Thu, Jul 22, 2010 at 11:58:14AM -0700, Guenter Roeck wrote:
> > > You use the argument that there may be other package level sensors in the future.
> > > Are there any plans for this, or is this just a theory ?
> >
> > Not just a theory. Sandy Bridge already implements other package level sensors.
> > If really need to know exactly which sensors are implemented, we might go
> > through a channel before releasing the info.
> >
> > > Next question is how to handle future sensor types. One hwmon instance per sensor,
> > > additional sensors in this driver, or even a new driver ?
> >
> > Currently package level thermal just reports the maximum temperature across
> > the package. Which sensor is reporting the highest temperature is not exposed.
>
> So this isn't a real physical sensor, but more of a meta-sensor? If
> this is a case, then we don't need support for this at all. User-space
> can compute a maximum by itself, we don't need a dedicated kernel
> driver for that.
>
> > > We had was a separate discussion if the coretemp driver should be redesigned
> > > to one instance per CPU. The package sensor would fit into that model,
> > > since you would have
> > >
> > > coretemp-isa-0000
> > > Core0
> > > Core1
> > > ...
> > > CoreN
> > > Package
> > >
> > > coretemp-isa-0001
> > > Core0
> > > Core1
> > > ...
> > > CoreM
> > > Package
> > >
> > > I personally would prefer that approach. It would avoid ambiguity associating Package X
> > > with specific cores, and it would also easily expand to additional non-core future sensors.
>
> For the records, I totally support this approach. I want the coretemp
> driver to be updated to present a single hwmon device per CPU, no
> matter what happens to the "package temperature".
>
I might spend some time rewriting the coretemp driver as described above,
unless someone else picks it up, and unless there is opposition.
Obviously, that won't include the package sensor since there is now
a separate driver for it.
Guenter
next prev parent reply other threads:[~2010-08-19 16:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <94E56C79ECC49A4B87113985F1FEBA8D03F8AE2A4B@bgsmsx502.gar.corp.intel.com>
[not found] ` <4C485DF1.5050407@linux.intel.com>
2010-07-22 16:21 ` [lm-sensors] [PATCH 1/5] Package Level Thermal Control and Power Fenghua Yu
2010-07-22 16:21 ` [PATCH 1/5] Package Level Thermal Control and Power Limit Notification: feature enabling Fenghua Yu
2010-07-22 16:21 ` [lm-sensors] [PATCH 2/5] Package Level Thermal Control and Power Fenghua Yu
2010-07-22 16:21 ` [PATCH 2/5] Package Level Thermal Control and Power Limit Notification: pkgtemp hwmon driver Fenghua Yu
2010-07-22 16:22 ` [lm-sensors] [PATCH 3/5] Package Level Thermal Control and Power Fenghua Yu
2010-07-22 16:22 ` [PATCH 3/5] Package Level Thermal Control and Power Limit Notification: thermal throttling Fenghua Yu
2010-07-22 16:22 ` [lm-sensors] [PATCH 4/5] Package Level Thermal Control and Power Fenghua Yu
2010-07-22 16:22 ` [PATCH 4/5] Package Level Thermal Control and Power Limit Notification: power limit notification Fenghua Yu
2010-07-22 16:22 ` [lm-sensors] [PATCH 5/5] Package Level Thermal Control and Power Fenghua Yu
2010-07-22 16:22 ` [PATCH 5/5] Package Level Thermal Control and Power Limit Notification: pkgtemp doc Fenghua Yu
2010-07-22 17:27 ` [lm-sensors] [PATCH 5/5] Package Level Thermal Control and Guenter Roeck
2010-07-22 17:27 ` [PATCH 5/5] Package Level Thermal Control and Power Limit Notification: pkgtemp doc Guenter Roeck
2010-07-22 17:52 ` [lm-sensors] [PATCH 5/5] Package Level Thermal Control and Fenghua Yu
2010-07-22 17:52 ` [PATCH 5/5] Package Level Thermal Control and Power Limit Notification: pkgtemp doc Fenghua Yu
2010-07-22 18:58 ` [lm-sensors] [PATCH 5/5] Package Level Thermal Control and Guenter Roeck
2010-07-22 18:58 ` [PATCH 5/5] Package Level Thermal Control and Power Limit Notification: pkgtemp doc Guenter Roeck
2010-07-22 21:21 ` [lm-sensors] [PATCH 5/5] Package Level Thermal Control and Fenghua Yu
2010-07-22 21:21 ` [PATCH 5/5] Package Level Thermal Control and Power Limit Notification: pkgtemp doc Fenghua Yu
2010-08-19 15:46 ` [lm-sensors] [PATCH 5/5] Package Level Thermal Control and Jean Delvare
2010-08-19 15:46 ` [PATCH 5/5] Package Level Thermal Control and Power Limit Notification: pkgtemp doc Jean Delvare
2010-08-19 16:27 ` Guenter Roeck [this message]
2010-08-19 16:27 ` Guenter Roeck
2010-08-19 20:51 ` [lm-sensors] [PATCH 5/5] Package Level Thermal Control and Fenghua Yu
2010-08-19 20:51 ` [PATCH 5/5] Package Level Thermal Control and Power Limit Notification: pkgtemp doc Fenghua Yu
2010-08-19 21:06 ` [lm-sensors] [PATCH 5/5] Package Level Thermal Control and Guenter Roeck
2010-08-19 21:06 ` [PATCH 5/5] Package Level Thermal Control and Power Limit Notification: pkgtemp doc Guenter Roeck
2010-08-20 8:33 ` [lm-sensors] [PATCH 5/5] Package Level Thermal Control and Jean Delvare
2010-08-20 8:33 ` [PATCH 5/5] Package Level Thermal Control and Power Limit Notification: pkgtemp doc Jean Delvare
2010-08-20 16:58 ` [lm-sensors] [PATCH 5/5] Package Level Thermal Control and Fenghua Yu
2010-08-20 16:58 ` [PATCH 5/5] Package Level Thermal Control and Power Limit Notification: pkgtemp doc Fenghua Yu
2010-08-20 18:39 ` [lm-sensors] [PATCH 5/5] Package Level Thermal Control and H. Peter Anvin
2010-08-20 18:39 ` [PATCH 5/5] Package Level Thermal Control and Power Limit Notification: pkgtemp doc H. Peter Anvin
2010-08-21 10:02 ` [lm-sensors] [PATCH 5/5] Package Level Thermal Control and Jean Delvare
2010-08-21 10:02 ` [PATCH 5/5] Package Level Thermal Control and Power Limit Notification: pkgtemp doc 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=20100819162719.GB4160@ericsson.com \
--to=guenter.roeck@ericsson.com \
--cc=fenghua.yu@intel.com \
--cc=gong.chen@linux.intel.com \
--cc=hpa@linux.intel.com \
--cc=huaxu.wan@intel.com \
--cc=khali@linux-fr.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.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.