On Thursday, October 29, 2015 05:57:19 PM Viresh Kumar wrote:
Hi Rafael,
As suggested by you yesterday, I have updated the governor core to keep per-cpu timers and a shared work for the entire policy.
More details are present in the changelogs, hope they are somewhat better this time.
I have tested it with the test-suite, that I created sometime back while fixing locking issues in governors.. Tried all kind of stuff in parallel that could have broken it (those are the testcases that separate people reported over time, around governors). It works fine.
The first one is a bug fix really, which I noticed today only :), next three are minor cleanups to prepare for the big change. Fourth one is the main patch that does the conversion and the final one is cherry-picked from the last series as that was still relevant.
This is rebased over: pm/bleeding-edge + "[PATCH V4] cpufreq: governor: Quit work-handlers early if governor is stopped", which I sent separately this morning with the changelog you suggested.
Please see if this meets your expectations or not :)
I like this set overall, except for the useless code shuffling in the first patch. Can you please update this one so it doesn't move code it has no reason to move and resend?
Thanks, Rafael