From: Greg KH <greg@kroah.com>
To: "V, Sankara Narayanan" <sankara.narayanan.v@intel.com>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: Power event notification patch
Date: Fri, 6 Jul 2007 11:41:53 -0700 [thread overview]
Message-ID: <20070706184153.GA4486@kroah.com> (raw)
In-Reply-To: <67670A5CEA5C374B8E7B16D7DC55F953012473FF@bgsmsx413.gar.corp.intel.com>
On Thu, Jul 05, 2007 at 05:31:33PM +0530, V, Sankara Narayanan wrote:
> Hi Folks,
>
>
>
> Here is a simple patch for power event notification to user-space
> applications. Basically, what it does is notify the user-space
> applications that the system is going to a low power state
> (Suspend-to-RAM and Suspend-to-Disk) and resume from that state. This is
> useful for the user-space applications to do some significant action
> when the system goes to the low power state (like saving an unsaved
> file). The user-space objects can form a netlink socket and listen to
> these events. It is done through a kobject-netlink socket. For this I
> have used the kobject_uevent system call, posting the notification to
> user space with standby, hibernate and resume in the action parameter of
> the kobject_uevent call (mapped to KOBJ_S3, KOBJ_S4 and KOBJ_RESUME
> enums). Appreciate your comments on the patch.
As others have stated, this is not acceptable for a wide range of
reasons.
Not the least being that even if you did implement this, you would need
to be listening to the dbus notification of this message, and so, just
do it all in userspace anyway, no kernel involvement is needed.
Oh, and the names S3, S4, don't mean much for non-intel based
processors, so that's also not acceptable.
thanks,
greg k-h
next prev parent reply other threads:[~2007-07-06 18:41 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
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 [this message]
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=20070706184153.GA4486@kroah.com \
--to=greg@kroah.com \
--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