[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20100821120250.1a992b7d@hyperion.delvare>
Date: Sat, 21 Aug 2010 12:02:50 +0200
From: Jean Delvare <khali@...ux-fr.org>
To: Fenghua Yu <fenghua.yu@...el.com>
Cc: Guenter Roeck <guenter.roeck@...csson.com>,
Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...ux.intel.com>,
"Brown, Len" <len.brown@...el.com>,
Chen Gong <gong.chen@...ux.intel.com>,
"Wan, Huaxu" <huaxu.wan@...el.com>,
lkml <linux-kernel@...r.kernel.org>,
"lm-sensors@...sensors.org" <lm-sensors@...sensors.org>
Subject: Re: [PATCH 5/5] Package Level Thermal Control and Power Limit
Notification: pkgtemp doc
One more thing...
On Thu, 19 Aug 2010 13:51:20 -0700, Fenghua Yu wrote:
> The pkgtemp reports thermal status for a set of sensors in a package. Please
> note the sensors in a package are not limited to processor sensors which are
> handled by coretemp. The sensors in a package also include gfx sensors, cache
> sensors, memory controllor sensors which are not handled by any hwmon drivers.
By "package" you mean CPU package, right? So by "gfx sensors" and
"memory controllor sensors", you refer to features possibly embedded
into the CPU package, not sensors outside the CPU, right?
> OS gets maximum package thermal status only from MSR PACKAGE_THERM_STATUS.
> There is no detailed thermal info for each sensor in a package. User-space
> can't compute a maximum by itself. So a piece of kernel driver code, whether
> a seperate driver or a integrated driver, is necessary if user-space wants to
> know thermal status of a package.
OK, now I understand, thanks for the clarification.
--
Jean Delvare
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists