* Stanislav Meduna | 2014-04-16 00:08:49 [+0200]: >Hmm... how is it in the rt-case guaranteed that the timer interrupt >does not preempt someone trying to modify the timer? The run_local_timers >looks to have arrived via hardirq context. The spinlock in the tvec_base >is a normal one and spin_lock_irqsave does not disable interrupts >on rt, right? this is, erm, harmless. We grab the timer lock via trylock in hardirq context. If the lock is already taken then we fail to get it we go for plan B. According to lockdep a trylock should not fail on UP. This is true in general except for this timer case. I was thinking abour disabling this lockdep check… Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
