Re: [lng-odp] [PATCH] timers: fix off by one tick in timer expiration processing

2016-10-17 Thread Maxim Uvarov
Merged. On 10/14/16 14:45, Mike Holmes wrote: also need to put Fixes https://bugs.linaro.org/show_bug.cgi?id=2552 I put this link to git log. Maxim. Into the patch description, maybe that can happen as it is pushed ? On 13 October 2016 at 17:46, Bill Fischofer wrote: Since this is a bug

Re: [lng-odp] [PATCH] timers: fix off by one tick in timer expiration processing

2016-10-14 Thread Mike Holmes
also need to put Fixes https://bugs.linaro.org/show_bug.cgi?id=2552 Into the patch description, maybe that can happen as it is pushed ? On 13 October 2016 at 17:46, Bill Fischofer wrote: > Since this is a bug fix, please open a Bug for it so that this can be > tracked as a defect closure. > > O

Re: [lng-odp] [PATCH] timers: fix off by one tick in timer expiration processing

2016-10-13 Thread Bill Fischofer
Since this is a bug fix, please open a Bug for it so that this can be tracked as a defect closure. On Thu, Oct 13, 2016 at 4:18 PM, Brian Brooks wrote: > A timer pool's tick starts at t0 (zero). Once the first period has passed, > the timer pool is scanned for any timers that have expired since

[lng-odp] [PATCH] timers: fix off by one tick in timer expiration processing

2016-10-13 Thread Brian Brooks
A timer pool's tick starts at t0 (zero). Once the first period has passed, the timer pool is scanned for any timers that have expired since t0 + 1. Current code does an atomic fetch increment on the tick, but uses the previous tick during timer expiration processing. What is needed is the previous