From: Len Brown <len.brown@intel.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Dax Kelson <dax@gurulabs.com>,
trenn@suse.de, seife@suse.de,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Allow userspace do something special on overtemp
Date: 12 Aug 2004 18:51:21 -0400 [thread overview]
Message-ID: <1092351080.5021.198.camel@dhcppc4> (raw)
In-Reply-To: <20040812202401.GB14556@elf.ucw.cz>
On Thu, 2004-08-12 at 16:24, Pavel Machek wrote:
> Hi!
>
> > > > I think I'd rather see the calls to usermode deleted
> > > > instead of extended -- unless there is a reason that
> > > > the general event -> acpid method can't work.
> > >
> > > See above, switching to acpid would break all the existing
> > > setups... in stable series.
> >
> > ah, the price of progress.
> >
> > I'm confident that the distros can figure out how to
> > update the (neglected) acpid scripts at the same time as
> > (or before) the kernel update.
>
> * not everyone is running distro
>
> * people update their kernels more often then their distros
>
> * not everyone wants to run acpid or equivalent (I don't, for example)
>
> * it is still change in stable series.
> * it is pretty subtle change, you are not going to notice it is broken
> unless you actually run critical.
>
> > If they can't, then ACPI critical shutdown will fail
> > (maybe on some systems not such a bad thing;-)
> > and TM1 will kick in, and if that doesn't work, TM2
> > will kick in, and if that doesn't work the processor
> > will disable itself.
>
> hmm, yes, but it still would be nice to properly shutdown instead of
> fail.
The reality is that most of the critical temperature events
are false positives, and for those that are not, the hardware
will keep itself from burning even when the OS control fails.
If we confuse some self-supporting kernel types, that is too bad.
If they're supporting themselves, they should read the change logs
for the kernels that they download. I don't think
this is of a magnitude that it needs to wait for 2.7 to be fixed.
-Len
next prev parent reply other threads:[~2004-08-12 22:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 8:53 Allow userspace do something special on overtemp Pavel Machek
2004-08-11 9:03 ` Arjan van de Ven
2004-08-11 9:06 ` Pavel Machek
2004-08-11 14:49 ` Len Brown
2004-08-11 14:52 ` Wichert Akkerman
2004-08-11 15:28 ` Thomas Renninger
2004-08-11 21:08 ` Kronos
2004-08-11 20:26 ` Pavel Machek
2004-08-11 9:18 ` Måns Rullgård
2004-08-11 18:22 ` Olaf Hering
[not found] ` <411A239C.8060606@blue-labs.org>
2004-08-11 20:22 ` Pavel Machek
2004-08-12 0:08 ` Dax Kelson
2004-08-12 3:29 ` Len Brown
2004-08-12 7:40 ` Pavel Machek
2004-08-12 14:28 ` Len Brown
2004-08-12 20:24 ` Pavel Machek
2004-08-12 22:51 ` Len Brown [this message]
2004-08-12 23:21 ` Pavel Machek
2004-08-12 7:35 ` Pavel Machek
2004-08-12 15:19 ` Len Brown
2004-08-12 15:16 ` Randy.Dunlap
2004-08-12 15:50 ` Stefan Seyfried
2004-08-12 17:27 ` [ACPI] " Stefan Dösinger
2004-08-12 22:53 ` Len Brown
[not found] <fa.fd8nc62.oig6ao@ifi.uio.no>
[not found] ` <fa.g1p407b.1c569pj@ifi.uio.no>
2004-08-13 4:22 ` Robert Hancock
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=1092351080.5021.198.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=dax@gurulabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=seife@suse.de \
--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