RE: Power event notification patch

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dbus is a distro specific thing and you cannot be really dependent on
that if you are going for real time systems. Also, they have their own
bindings for the notification support (dbus-glib and dbus-qt). One more
drawback with dbus (apart from the above one), it will be another
redirection before our application receives the notification). Also, if
you say S3/S4 are PC oriented (or intel specific; It is mentioned in
ACPI spec.) terms, the suspend-to-ram and to disk is not necessarily PC
(or intel) oriented. 

Thanks,
Sankar.
-----Original Message-----
From: Greg KH [mailto:greg@xxxxxxxxx] 
Sent: Saturday, July 07, 2007 12:12 AM
To: V, Sankara Narayanan
Cc: linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx
Subject: Re:  Power event notification patch

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

_______________________________________________
linux-pm mailing list
linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/linux-pm

[Index of Archives]     [Linux ACPI]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [CPU Freq]     [Kernel Newbies]     [Fedora Kernel]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux