Re: [LNG] Re: [PATCH 12/14] hrtimer: don't emulate notifier call to initialize timer base

2014-03-26 Thread Viresh Kumar
On 26 March 2014 18:10, Srivatsa S. Bhat wrote: > I don't think this is such a good idea. Open-coding a part of that callback > in the init routine can lead to loop-holes down the road: We think that we are open-coding part of that callback here because it is implemented that way on the first des

Re: [PATCH 12/14] hrtimer: don't emulate notifier call to initialize timer base

2014-03-26 Thread Srivatsa S. Bhat
On 03/26/2014 04:51 PM, Viresh Kumar wrote: > In hrtimers_init() we need to call init_hrtimers_cpu() for boot CPU. For this, > currently we are emulating a call to hotplug notifier. Probably this was done > initially to get rid of code redundancy. But this sequence always called a > single routine,

[PATCH 12/14] hrtimer: don't emulate notifier call to initialize timer base

2014-03-26 Thread Viresh Kumar
In hrtimers_init() we need to call init_hrtimers_cpu() for boot CPU. For this, currently we are emulating a call to hotplug notifier. Probably this was done initially to get rid of code redundancy. But this sequence always called a single routine, i.e. init_hrtimers_cpu(), and so calling that routi