I want to modify the cpufreq_transition_notifier_list. Currently it is a
source of problems during swsusp, because the suspend and resume methods
invoke the notifier chain at a time when the down_read() operation
protecting the chain is not legal.
If the notifier chain is protected by SRCU ("Sleepable RCU", recently
added to -mm) instead of an rwsem, the problems would go away. However
SRCU requires runtime initialization. This means the notifier chain's
head has to be initialized before any listeners register on it and before
the chain is ever invoked.
Can anyone tell me where a good place would be to do the initialization?
It has to be early enough that nobody has used the transition notifier
list but late enough that per-CPU data can be allocated.
Alan Stern
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
