Hi,
This is rather extreme, but I think that we should make the scheduler paths as
lightweight as reasonably possible.
[1/2] removes the atomic work counter incrementation from gov_cancel_work() as
it is not necessary any more.
[2/2] changes the way work items are handled by dbs_update_util_handler() and
dbs_work_handler() to avoid extra atomic operations in cases when they
aren't really necessary (policy objects serving one CPU only).
On top of the pm-cpufreq-test branch of linux-pm.git. Lightly tested, but
I don't have systems where policy objects are shared.
Thanks,
Rafael
