On Sat 2007-07-21 11:50:01, Pavel Machek wrote:
> Hi!
>
> > > Hello Rafael,
> >
> > Thanks for all of the patches so far. :-)
> >
> > > Yet another patch in the suspend2 feature-set series.
> > > It sets cpufreq to maximum during the cycle.
> > > It is important to finish the process as quickly as possible (human
> > > engineer issue :) )
> > > When running on batteries it may take forever without this...
> > >
> > > Please consider to apply.
> >
> > Hmm, I'm not sure. I'd like to know what people on the list think about it.
> > Stefan, Pavel?
>
> I'm not sure it is good idea. We should either let cpu frequency
> scaling do its job during suspend (it should just scale to the max
> when it sees cpu load), or force it to _minimum_. Machines will
> overheat on max cpufreq, and they may overload their batteries.
Okay, so this is done from userland, not from kernel.
Does cpu frequency scaling work properly after we snapshot the system?
If yes, we should not need to do this.
If not, this is unsafe.
Which case is it?
We may need to fix cpufreq a bit...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Suspend-devel mailing list
Suspend-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/suspend-devel
