On 9 April 2015 at 01:41, Thomas Gleixner wrote:
> I'm really not too excited about this incomprehensible macro mess and
> especially not about the code it generates.
>
> x86_64 i386ARM power
>
> Mainline76686942807710253
>
> + Patch 8068
On Tue, 7 Apr 2015, 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.
>
>
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
>
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
On Tue, 7 Apr 2015, 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
On 9 April 2015 at 01:41, Thomas Gleixner t...@linutronix.de wrote:
I'm really not too excited about this incomprehensible macro mess and
especially not about the code it generates.
x86_64 i386ARM power
Mainline76686942807710253
+ Patch
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
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
8 matches
Mail list logo