From: Benjamin Herrenschmidt <bh40@calva.net>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>,
Avery Pennarun <apenwarr@worldvisions.ca>
Cc: <linuxppc-dev@lists.linuxppc.org>, <debian-powerpc@lists.debian.org>
Subject: Re: apmd and other archs
Date: Fri, 24 Nov 2000 14:40:41 +0100 [thread overview]
Message-ID: <19341019071225.5885@192.168.1.2> (raw)
In-Reply-To: <Pine.LNX.4.10.10011230936470.22746-100000@opal.biophys.uni-duesseldorf.de>
>> Not APM support exactly... simply support for the same interface.
Just like
>> powermacs have totally different sound systems and still use /dev/dsp.
>> /proc/apm and /dev/apm_bios are so simple that it should be easy to
convince
>> any power management system to provide those API's.
>
>The info logged to /proc/apm is currently logged to /etc/power/apm. I have
>no idea what /dev/apm does aside from providing that log info, and I have
>no clue what /dev/apm_bios does, either. There should be no major problems
>duplicating the pmu logging code in the kernel, and interfacing that with
>some apm glue code, assuming the apm interface is reasonably architecture
>independent. I just don't see a good reason to change from pmud to apmd,
>if that's what you're suggesting.
At least one reason: the current pmud does continuous polling of the PMU
via /dev/pmu. On newer (core99) machines, the PMU itself will send
messages to the CPU when any environement info change (battery status,
lid closed, ...). We currently don't use this feature and so end up
communicating with the PMU more than we would really need.
We can "fix" that by either having the PMU driver on core99 continuously
send those infos via /dev/pmu without explicit request. It may also be
interesting to replace this by a kernel thread. That would allow more
flexibility in communicating with userland (things like signaling
processes that asked for it to be notified of a sleep request, etc...).
One other issue we have with sleep is that we need to prevent the kernel
to do a bunch of thigns while going to sleep. scheduling from within the
sleep ioctl is dangerous, but will happen occasionally, especially when
sleeping & waking up the IDE layer.
I beleive it should be possible to hack the scheduler so that only our
sleep thread gets scheduled at all (disabling scheduling on the main CPU
and freezing other CPUs in sleep loops) during the sleep & wakeup process.
Any better ideas ?
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-11-24 13:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20001122143042.A28078@worldvisions.ca>
2000-11-23 8:47 ` apmd and other archs Michael Schmitz
2000-11-23 10:09 ` Avery Pennarun
2000-11-23 10:40 ` Michel Dänzer
2000-11-23 11:08 ` Avery Pennarun
2000-11-23 11:15 ` Michael Schmitz
2000-11-23 11:31 ` Avery Pennarun
2000-11-23 13:36 ` Michael Schmitz
2000-11-23 14:18 ` Gabriel Paubert
2000-11-23 18:40 ` Michael Schmitz
2000-11-24 14:23 ` Gabriel Paubert
2000-11-24 18:29 ` Takashi Oe
2000-11-24 14:47 ` Olaf Hering
2000-11-24 15:23 ` Michael Schmitz
2000-11-23 11:37 ` Gabriel Paubert
2000-11-23 13:32 ` Tony Mantler
2000-11-23 14:12 ` Gabriel Paubert
2000-11-23 14:24 ` Adrian Cox
2000-11-24 10:07 ` Gabriel Paubert
2000-11-24 2:42 ` Josh Huber
2000-11-23 11:11 ` Michael Schmitz
2000-11-23 13:36 ` Hadess
2000-11-23 13:54 ` Michael Schmitz
2000-11-27 13:23 ` Michael Schmitz
2000-11-27 14:53 ` Benjamin Herrenschmidt
2000-11-27 15:34 ` Michael Schmitz
2000-11-27 20:50 ` Michael Schmitz
2000-11-24 13:51 ` Benjamin Herrenschmidt
2000-11-24 15:11 ` Bastien Nocera
2000-11-24 13:40 ` Benjamin Herrenschmidt [this message]
2000-11-24 14:29 ` Gabriel Paubert
2000-11-24 15:33 ` Benjamin Herrenschmidt
2000-11-24 16:26 ` Gabriel Paubert
2000-11-24 17:31 ` Benjamin Herrenschmidt
2000-11-24 17:56 ` Geert Uytterhoeven
2000-11-24 19:27 ` Gabriel Paubert
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=19341019071225.5885@192.168.1.2 \
--to=bh40@calva.net \
--cc=apenwarr@worldvisions.ca \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schmitz@opal.biophys.uni-duesseldorf.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).