From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: swsusp: don't eat ide disks
Date: 08 Nov 2002 12:09:03 +0100 [thread overview]
Message-ID: <1036753743.5029.64.camel@zion> (raw)
In-Reply-To: <3205.1036707953@passion.cambridge.redhat.com>
On Thu, 2002-11-07 at 23:25, David Woodhouse wrote:
>
> Actually I do have boxes on which I "echo 1 > /proc/sys/pm/suspend" to make
> them sleep. Pavel's right though -- that's not a particularly wonderful
> interface either. Using sys_reboot() makes some sense to me.
>
> But stuff like battery info in /proc/acpi just has no excuse.
(David: resent, forgot the list)
We need more than just an interface to put the machine to sleep
in fact.
We also need a way for userland to be notified that the machine
will sleep and that it woke up. And if possible in a blocking
way (that is the sleep process waits for the notified userland
app to ack, or refuse).
Typically, that happens today with X via /dev/apm_bios. On PPC,
I emulate this interface, I think ARM does as well. But that
should definitely be replaced by something. Maybe not in kernel
though, that all depends if the kernel can be the initiator
of a suspend process or not.
If it can (upon request from the firmware or whatever), then we need
such an API provided by the kernel. If we decide only userland can
trigger suspend, then we probably need to design some PM daemon
that provides a known interface.
It's very important for apps like X that bang the HW directly to
be notified of the sleep process properly.
Ben.
next prev parent reply other threads:[~2002-11-08 11:00 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-07 18:26 swsusp: don't eat ide disks Grover, Andrew
2002-11-07 22:25 ` David Woodhouse
2002-11-08 11:09 ` Benjamin Herrenschmidt [this message]
2002-11-10 11:54 ` Pavel Machek
2002-11-11 6:38 ` David Woodhouse
2002-11-12 17:41 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-11-02 18:47 Pavel Machek
2002-11-02 19:39 ` Linus Torvalds
2002-11-02 20:06 ` Alan Cox
2002-11-02 20:25 ` Pavel Machek
2002-11-02 22:04 ` Alan Cox
2002-11-03 20:11 ` Pavel Machek
2002-11-04 1:04 ` Rik van Riel
2002-11-06 12:34 ` Pavel Machek
2002-11-03 14:57 ` benh
2002-11-03 16:25 ` Alan Cox
2002-11-03 16:24 ` benh
2002-11-03 16:36 ` Alan Cox
2002-11-04 7:47 ` benh
2002-11-03 20:12 ` Pavel Machek
2002-11-03 21:33 ` Alan Cox
2002-11-03 22:09 ` Pavel Machek
2002-11-03 22:41 ` Alan Cox
2002-11-03 22:27 ` Pavel Machek
2002-11-03 23:56 ` Alan Cox
2002-11-04 8:16 ` benh
2002-11-04 13:33 ` Alan Cox
2002-11-03 22:48 ` Linus Torvalds
2002-11-03 22:53 ` Linus Torvalds
2002-11-04 8:08 ` benh
2002-11-04 14:59 ` Linus Torvalds
2002-11-04 15:27 ` Benjamin Herrenschmidt
2002-11-04 9:44 ` Jens Axboe
2002-11-04 13:37 ` Alan Cox
2002-11-03 22:56 ` Pavel Machek
2002-11-03 23:38 ` Linus Torvalds
2002-11-06 13:57 ` Pavel Machek
2002-11-04 7:57 ` benh
2002-11-04 9:39 ` Jens Axboe
2002-11-04 9:50 ` Jens Axboe
2002-11-07 13:06 ` David Woodhouse
2002-11-07 16:15 ` Pavel Machek
2002-11-07 16:18 ` David Woodhouse
2002-11-07 20:52 ` Pavel Machek
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=1036753743.5029.64.camel@zion \
--to=benh@kernel.crashing.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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