From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Thomas Renninger <trenn@suse.de>,
"R, Durgadoss" <durgadoss.r@intel.com>,
"jdelvare@novell.com" <jdelvare@novell.com>,
Len Brown <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
Kay Sievers <kay.sievers@vrfy.org>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-trace-users@vger.kernel.org"
<linux-trace-users@vger.kernel.org>
Subject: Re: Thermal kernel events API to userspace - Was: Re: thermal: Avoid CONFIG_NET compile dependency
Date: Tue, 25 Jan 2011 13:51:52 -0200 [thread overview]
Message-ID: <20110125155152.GC14803@khazad-dum.debian.net> (raw)
In-Reply-To: <1295942269.1866.1201.camel@rui>
On Tue, 25 Jan 2011, Zhang Rui wrote:
> On Tue, 2011-01-25 at 00:07 +0800, Henrique de Moraes Holschuh wrote:
> > > > > Also, the thermal_aux0 and _aux1, we can use the final format specified by you.
> > > > > enum events {
> > > > > THERMAL_CRITICAL,
> > > > > /* user defined thermal events */
> > > > > THERMAL_USER_AUX0,
> > > > > THERMAL_USER_AUX1,
> > > > > THERMAL_DEV_FAULT,
> > > > > };
> >
> > Please give us at least two levels of thermal alarm: critical and emergency
> > (or warning and critical -- it doesn't matter much, as long as there are at
> > least two levels, and which one comes first is defined by the
> > specification). I'd have immediate use for them on thinkpads.
> >
> > It is probably best to have three levels (warning, critical, emergency).
> > Best not to tie the API/ABI to the notion of "too hot", one can also alarm
> > when it starts to get to cold.
> >
> when it's the "too hot" case, what kind of action should be taken upon
> the warning/critical/emergency events?
> I mean what's the difference between these three levels.
*ASSUMING* it is monitoring the box (which is a damn big assumption, and
should be stated outright):
Warning: do something to stop generating so much heat, warn user, try to
increase cooling. Let userspace bother with this.
Critical: *STOP* generating so much heat (throttle cpu, throttle GPU,
shutdown non-critical devices, etc). Increase cooling to max. WARN the
user that a machine emergency exists and shutdown is imminent, and that he
has to power off or sleep to ram *NOW*.
Emergency: emergency sync, and initiate immediate suspend to ram. If that
fails, initiate emergency powerdown.
Likely one wants kernel notifiers for this stuff, too, so that we can have
in-kernel handlers (optional or not, configurable or not, that is orthogonal
to the issue) that can try to do something to help.
--
"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
next prev parent reply other threads:[~2011-01-25 15:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 10:52 thermal: Avoid CONFIG_NET compile dependency R, Durgadoss
2011-01-21 12:12 ` Thomas Renninger
2011-01-24 1:22 ` Zhang Rui
2011-01-24 4:39 ` R, Durgadoss
2011-01-24 10:35 ` Thomas Renninger
2011-01-24 13:07 ` Thermal kernel events API to userspace - Was: " Thomas Renninger
2011-01-24 16:07 ` Henrique de Moraes Holschuh
2011-01-25 7:57 ` Zhang Rui
2011-01-25 10:12 ` Thomas Renninger
2011-01-25 16:10 ` Henrique de Moraes Holschuh
2011-01-26 7:14 ` Zhang, Rui
2011-01-26 21:28 ` Henrique de Moraes Holschuh
2011-01-25 15:51 ` Henrique de Moraes Holschuh [this message]
2011-01-25 4:47 ` R, Durgadoss
2011-01-25 9:20 ` Thomas Renninger
2011-01-25 9:45 ` R, Durgadoss
2011-01-25 9:48 ` Jean Delvare
2011-01-25 13:43 ` Guenter Roeck
2011-01-25 16:18 ` Thomas Renninger
2011-01-25 16:25 ` Guenter Roeck
2011-01-27 9:48 ` Thomas Renninger
2011-01-27 13:34 ` R, Durgadoss
2011-01-27 13:59 ` Thomas Renninger
2011-01-25 7:54 ` Zhang Rui
2011-01-25 8:43 ` R, Durgadoss
2011-01-24 0:34 ` Zhang Rui
-- strict thread matches above, loose matches on Subject: below --
2011-01-25 11:14 Thermal kernel events API to userspace - Was: " R, Durgadoss
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=20110125155152.GC14803@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=durgadoss.r@intel.com \
--cc=jdelvare@novell.com \
--cc=kay.sievers@vrfy.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=rui.zhang@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox