[lkml]   [1999]   [Mar]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] recover lost ticks

On Tue, 16 Mar 1999, Vojtech Pavlik wrote:

> Anyway, for another example, I've checked the Logitech joystick driver. It
> needs to send an init sequence to the joystick, which consists of a series
> of various delays and writes to the joystick port. It needs to be timed
> precisely, and, so it can't allow an interrupts to happen in the middle of
> the udelay() and make it take more time. The whole sequence takes 6+11+7+9 =
> 33 ms of cli() time. I could base this on gettimeofday() or PIT reading, and
> forget the cli(), but still an interrupt at the wrong time would kill the
> timing ...
> Just two examples of bad behaving hardware.

thanks for explaining those two cases. For the second one, i dont think an
init sequence is too critical. (it would be critical i think if we lost a
tick for every joystick event)

hm, would it help if you had very precise and high-frequency timers, but
with the restriction that they are NMI so they have to be used very
carefully (and with a different timer interface)? On pentiums and up we
can have periodic NMI interrupts generated by the CPU. Sustaining 100 khz
is no problem with those. The problem is, this trick is pretty much

-- mingo

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:50    [W:0.063 / U:12.488 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site