public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.org>
To: "V, Sankara Narayanan" <sankara.narayanan.v@intel.com>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: Power event notification patch
Date: Thu, 5 Jul 2007 14:34:47 +0200	[thread overview]
Message-ID: <200707051434.47970.oliver@neukum.org> (raw)
In-Reply-To: <67670A5CEA5C374B8E7B16D7DC55F95301247414@bgsmsx413.gar.corp.intel.com>

Am Donnerstag, 5. Juli 2007 schrieb V, Sankara Narayanan:
> 1. Isn't it the kernel which is finally initiating a low power sleep
> state? So, I added it in kernel/power/main.c where the kernel does all
> the suspend related activities.

Not really. The kernel takes the system to sleep if somebody with
the proper credentials tells it to do so. The kernel doesn't take the
initiative.

So the most obvious place to do the notification is with the entity
that initiates the sleep.

> 2. To answer your second question, we really can't guarantee. But even
> if you take Windows Vista (sorry linux enthusiasts for referring windows
> here) or any other non-UNIX operating systems (which has this power
> event notification), they really do not guarantee it. But, it is an
> era-of-tera and the user space applications can do some minimal work
> like saving the app's last state in a .tmp file or so (like firefox if
> closed in an unclean way) to restore their state.

Well, we want to better than that other OS.

If you do this in user space, eg. the pm utilities, you can easily implement
policies like waiting x seconds for the rest of the system to respond.

	Regards
		Oliver

  reply	other threads:[~2007-07-05 12:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05 12:01 Power event notification patch V, Sankara Narayanan
2007-07-05 12:08 ` Oliver Neukum
2007-07-05 12:17   ` V, Sankara Narayanan
2007-07-05 12:34     ` Oliver Neukum [this message]
2007-07-05 12:44       ` V, Sankara Narayanan
2007-07-05 12:51         ` Oliver Neukum
2007-07-05 12:54         ` Igor Stoppa
2007-07-05 13:09           ` V, Sankara Narayanan
2007-07-05 13:12             ` Johannes Berg
2007-07-05 13:17               ` V, Sankara Narayanan
2007-07-05 13:28                 ` Johannes Berg
2007-07-05 13:33                   ` V, Sankara Narayanan
2007-07-06 10:46                     ` Johannes Berg
2007-07-05 13:56                   ` Scott Preece
2007-07-05 13:22               ` Johannes Berg
2007-07-05 13:20             ` Igor Stoppa
2007-07-05 13:39               ` V, Sankara Narayanan
2007-07-05 13:46                 ` Igor Stoppa
2007-07-05 12:48       ` Johannes Berg
2007-07-06 18:41 ` Greg KH
2007-07-09  4:34   ` V, Sankara Narayanan
2007-07-09 16:34     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2007-07-05 12:02 V, Sankara Narayanan

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=200707051434.47970.oliver@neukum.org \
    --to=oliver@neukum.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=sankara.narayanan.v@intel.com \
    /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