On Wed, Apr 19, 2017 at 08:50:39AM +0200, Peter Zijlstra wrote:
> On Tue, Apr 18, 2017 at 01:11:05PM +0200, Thomas Gleixner wrote:
> > Storing next event and determining whether the base is idle can be done in
> > __next_timer_interrupt().
> >
> > Preparatory patch for new call sites which need t
On Tue, Apr 18, 2017 at 01:11:05PM +0200, Thomas Gleixner wrote:
> Storing next event and determining whether the base is idle can be done in
> __next_timer_interrupt().
>
> Preparatory patch for new call sites which need this information as well.
>
> Signed-off-by: Thomas Gleixner
> ---
> ker
Storing next event and determining whether the base is idle can be done in
__next_timer_interrupt().
Preparatory patch for new call sites which need this information as well.
Signed-off-by: Thomas Gleixner
---
kernel/time/timer.c | 43 ---
1 file chang
3 matches
Mail list logo