8 Apr
2015
8 Apr
'15
12:10 p.m.
On Tue, Apr 07, 2015 at 07:40:53AM +0530, Viresh Kumar wrote:
At several instances we iterate over all possible clock-bases for a particular cpu-base. Whereas, we only need to iterate over active bases.
We already have per cpu-base 'active_bases' field, which is updated on addition/removal of hrtimers.
This patch creates for_each_active_base(), which uses 'active_bases' to iterate only over active bases.
This also updates code which iterates over clock-bases.
This Changelog is very thin on compelling reasons to do this. Not to mention you did no analysis on the code generated.