On Wed, Aug 04, 2010 at 09:32:16AM -0700, Paul E. McKenney wrote: > If this doesn't work for the Android folks for whatever reason, another > approach would be to do the freeze in user code, which could track > whether any user-level resources (pthread mutexes, SysV semas, whatever) > where held, and do the freeze on a thread-by-thread basis within each > "victim" application as the threads reach safe points. The main problem I see with the cgroups solution is that it doesn't seem to do anything to handle avoiding loss of wakeup events. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
