From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Integrating OS power management with the X server
Date: Mon, 25 Oct 2004 12:14:34 -0700 [thread overview]
Message-ID: <417D509A.8040305@root.org> (raw)
In-Reply-To: <1098727986.3996.65.camel@tyrosine>
Matthew Garrett wrote:
> On Mon, 2004-10-25 at 10:26 -0700, Nate Lawson wrote:
>>This interface works for apm (except that it only has NetBSD defines
>>currently) but is not implemented for ACPI. I'd like more information
>>as to what the X server actually does with this event. Is there any
>>situation where it actually needs to veto a suspend? Does it
>>potentially take seconds to save state? Does it need to access other
>>running subsystems or is it self-contained?
>
> At the moment, is it still the case that X will be unhappy if there are
> any DRI clients running when going through a suspend/resume cycle?
I don't know.
> If
> so, it sounds like the server ought to reject a suspend (or,
> alternatively, use the notification to kill clients).
Or better, properly implement saving state in DRI.
> In the future, I'd expect that some dbus-related system would be
> preferable - that way X doesn't get special cased, and any application
> with good cause could reject a suspend.
The existing bsd_apm.c works for NetBSD and is the same interface as APM
in FreeBSD. Basically, you open /dev/apm and get notification of
suspend requests. Then you can continue them by sending a suspend ioctl
or veto by just ignoring them. The problem is, there are some times in
ACPI when the userland cannot veto a suspend (i.e., critical battery or
system temperature). My plan is to initiate an unconditional suspend in
those cases from the kernel. Userland will have a chance to get the
notification but if it doesn't respond within some timeout (say a few
seconds), the kernel continues the suspend process.
The reason for my email is it's not clear what semantics X expects and
how much it even uses this interface.
--
Nate
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-25 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 17:26 Integrating OS power management with the X server Nate Lawson
[not found] ` <417D372C.3000107-Y6VGUYTwhu0@public.gmane.org>
2004-10-25 18:13 ` Matthew Garrett
2004-10-25 19:14 ` Nate Lawson [this message]
[not found] ` <417D509A.8040305-Y6VGUYTwhu0@public.gmane.org>
2004-10-25 21:17 ` Stefan Dösinger
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=417D509A.8040305@root.org \
--to=nate-y6vguytwhu0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.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