Dnia 3 stycznia 2010 22:29 "Rafael J. Wysocki" <rjw@xxxxxxx> napisał(a): > > > To put it in a different way, you apparently want the kernel to notify the user > > > space of an event originating from the user space and my question is why not > > > to set up the user space to generate the notification without relying on the > > > kernel to do that. > > > > Because now kernel know better what is going on. > > That's because it's just been told by the user space about that. > > Basically, you want something like this to happen: > > process A ->(suspend) kernel > kernel ->(suspending) process B > Yes. > where the kernel won't wait for process B to do whatever it has to do before > suspending. In my opinion it'd be better to do something like this > > process A ->(suspending) process B > process B ->(ack) process A > process A ->(suspend) kernel > > ... Please forget for a moment about pm-utils. I was thinking about sf like this: pm-notify is registered in pm_notifier_chain or called before pm_notifiers_chain pm-notify -> (suspending) all registerd processes some processes ->(ack) pm-notify after timeout ( 1s. could be ok) pm-notify will send NOTIFY_OK and kernel will cont. suspending It could be even UIO module but there are no pm events reachable there? If it is not clean, we must extend pm-utils or write something new (with backends dbus, ipc, scripts, ...) But You see? We still have no information from kernel about events (especialy resume) or maybe i dont see this ;/ Thanks for your understanding Rafael :) Best regards. Bartłomiej Zimoń PLD Linux, Kadu Team, FreeRunner user http://kadu-im.blogspot.com/ _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
