From: Thomas Renninger <trenn@suse.de>
To: Joey Lee <jlee@novell.com>
Cc: rui.zhang@intel.com, hmacht@suse.de, rwysocki@suse.de,
linux-acpi@vger.kernel.org
Subject: Re: [RFC] Shutdown on thermal HOT event if no userspace tool registered being able to do S4
Date: Tue, 30 Mar 2010 17:31:01 +0100 [thread overview]
Message-ID: <201003301831.01709.trenn@suse.de> (raw)
In-Reply-To: <4BB2BDA8020000230001594B@novprvlin0050.provo.novell.com>
On Tuesday 30 March 2010 18:12:40 Joey Lee wrote:
> Hi Thomas,
>
> 於 二,2010-03-30 於 10:23 +0100,Thomas Renninger 提到:
> > Hi,
...
> > Comments?
> > What userspace tools are candidates to implement this if this
> > makes sense?
> >
>
> HAL + pm-util or DeviceKit-power might the candidates. But, if there
> have no those component in userland, what will acpi thermal module do?
> Direct shutdown?
> And, how can kernel space know userland can do this job well? Might wait
> 10 seconds if system doesn't S4 or shutdown?
Yep, my idea is to e.g. provide:
/sys/class/thermal/S4_capable
By default you get:
cat /sys/class/thermal/S4_capable
0
and the thermal driver will call the same shutdown method
if the hot thermal tp is reached as if the critical is reached.
If pm-utils does:
echo 1 >/sys/class/thermal/S4_capable
it has to make sure it picks up acpi thermal hot event and initiates
S4. If S4 fails for whatever reasons (no swap,
stroking some kernel drivers fails, unmounting file systems fails, ...),
it has to make sure to force a system shutdown (just call /sbin/poweroff
the same way the kernel does currently with a critical thermal event?).
Emergency shutdown is then out of kernels hand (as it is currently for HOT
anyway which is dangerous).
Hmm, this is acpi specific, possibly it should be a new dir here:
/sys/firmware/acpi/thermal/S4_capable
or something else?
Thomas
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-30 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 16:12 [RFC] Shutdown on thermal HOT event if no userspace tool registered being able to do S4 Joey Lee
2010-03-30 16:31 ` Thomas Renninger [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-12 2:06 Joey Lee
2010-04-01 13:18 Joey Lee
2010-04-01 13:40 ` Kay Sievers
2010-03-30 9:23 Thomas Renninger
2010-03-31 0:14 ` Henrique de Moraes Holschuh
2010-04-12 2:38 ` Zhang Rui
2010-04-13 8:54 ` Thomas Renninger
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=201003301831.01709.trenn@suse.de \
--to=trenn@suse.de \
--cc=hmacht@suse.de \
--cc=jlee@novell.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=rwysocki@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;
as well as URLs for NNTP newsgroup(s).