Based on code inspection, it looks like a timer handler triggering a
reschedule in the path xntbase_tick - xntimer_tick_aperiodic /
xntimer_tick_periodic_inner - handler can cause problems, e.g. a
reschedule before all expired timers were processed. The timer core is
usually run atomically from an
On 06/17/2011 11:27 AM, Jan Kiszka wrote:
Based on code inspection, it looks like a timer handler triggering a
reschedule in the path xntbase_tick - xntimer_tick_aperiodic /
xntimer_tick_periodic_inner - handler can cause problems, e.g. a
reschedule before all expired timers were processed.
On 2011-06-17 12:58, Gilles Chanteperdrix wrote:
On 06/17/2011 11:27 AM, Jan Kiszka wrote:
Based on code inspection, it looks like a timer handler triggering a
reschedule in the path xntbase_tick - xntimer_tick_aperiodic /
xntimer_tick_periodic_inner - handler can cause problems, e.g. a
On Fri, 2011-06-17 at 13:03 +0200, Jan Kiszka wrote:
On 2011-06-17 12:58, Gilles Chanteperdrix wrote:
On 06/17/2011 11:27 AM, Jan Kiszka wrote:
Based on code inspection, it looks like a timer handler triggering a
reschedule in the path xntbase_tick - xntimer_tick_aperiodic /
On 2011-06-17 13:58, Philippe Gerum wrote:
On Fri, 2011-06-17 at 13:03 +0200, Jan Kiszka wrote:
On 2011-06-17 12:58, Gilles Chanteperdrix wrote:
On 06/17/2011 11:27 AM, Jan Kiszka wrote:
Based on code inspection, it looks like a timer handler triggering a
reschedule in the path xntbase_tick -
On Fri, 2011-06-17 at 14:11 +0200, Jan Kiszka wrote:
On 2011-06-17 13:58, Philippe Gerum wrote:
On Fri, 2011-06-17 at 13:03 +0200, Jan Kiszka wrote:
On 2011-06-17 12:58, Gilles Chanteperdrix wrote:
On 06/17/2011 11:27 AM, Jan Kiszka wrote:
Based on code inspection, it looks like a timer
