From: Pavel Machek <pavel@suse.cz>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "David S. Miller" <davem@redhat.com>,
"Grover, Andrew" <andrew.grover@intel.com>,
"'John Fremlin'" <chief@bandits.org>,
"'Simon Richter'"
<Simon.Richter@phobos.fachschaften.tu-muenchen.de>,
"Acpi-PM (E-mail)"
<linux-power@phobos.fachschaften.tu-muenchen.de>,
"'Pavel Machek'" <pavel@suse.cz>,
Andreas Ferber <aferber@techfak.uni-bielefeld.de>,
linux-kernel@vger.kernel.org
Subject: Re: Let init know user wants to shutdown [linux-power] [linux-pm-devel] [linux-kernel-mailing-list] [some-other-list]
Date: Fri, 27 Apr 2001 12:58:45 +0200 [thread overview]
Message-ID: <20010427125845.C13099@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <15080.40123.543633.854889@pizda.ninka.net> <4148FEAAD879D311AC5700A0C969E89006CDDD9F@orsmsx35.jf.intel.com> <15080.40123.543633.854889@pizda.ninka.net> <17244.988362192@redhat.com>
In-Reply-To: <17244.988362192@redhat.com>; from dwmw2@infradead.org on Fri, Apr 27, 2001 at 10:03:12AM +0100
Hi!
> > You can break the whole power management problem down to "here are the
> > levels of low-power provided by the hardware, here are the idleness
> > triggers that may be monitored". That's it, nothing more.
> > This is powerful enough to do all the things you could want a pm layer
> > to do:
> >
> > 1) CPU's have been in their idle threads for X percent of
> > of the past measurement quantum, half clock the processors.
> >
> > 2) The user has hit the "sleep" trigger, spin down the disks,
> > reduce clock the cpus, bus, PCI controller and PCI devices.
>
> Often the 'sleep trigger' is an _absence_ of activity rather than anything
> explicit like a button being pressed. You need inactivity timers, and events
> which _reset_ those timers, on triggers like keyboard/touchscreen/serial
> input, etc.
I believe that at least thermal managment should be done in
kernelspace. You do not want to overheat your cpu because you
accidentally killed powerd, right?
Pavel
--
The best software in life is free (not shareware)! Pavel
GCM d? s-: !g p?:+ au- a--@ w+ v- C++@ UL+++ L++ N++ E++ W--- M- Y- R+
prev parent reply other threads:[~2001-04-27 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 22:52 Let init know user wants to shutdown Grover, Andrew
2001-04-26 22:10 ` David S. Miller
2001-04-27 9:03 ` Let init know user wants to shutdown [linux-power] [linux-pm-devel] [linux-kernel-mailing-list] [some-other-list] David Woodhouse
2001-04-27 10:58 ` Pavel Machek [this message]
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=20010427125845.C13099@atrey.karlin.mff.cuni.cz \
--to=pavel@suse.cz \
--cc=Simon.Richter@phobos.fachschaften.tu-muenchen.de \
--cc=aferber@techfak.uni-bielefeld.de \
--cc=andrew.grover@intel.com \
--cc=chief@bandits.org \
--cc=davem@redhat.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-power@phobos.fachschaften.tu-muenchen.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
all inboxes | Powered by JetHome®