On Fri, 22 Mar 2013, Oliver Nittka wrote: > The timing is fine most of the time, but putting the system under heavy > CPU and USB load leads to occasional glitches where the time between two > ioctl calls can be as high as 50ms. The kernel tracer is your friend. Enable the kernel function tracer and add a check into your application which detects the issue and then stops the trace. See the cyclictest source code for an example how to do that. Thanks, tglx -- 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
