On Thu, 30 May 2013, Ivo Sieben wrote: > When a threaded irq handler is installed the irq thread is initially created > on normal scheduling priority. Only after the the irq thread is woken up it > sets its priority to RT_FIFO MAX_USER_RT_PRIO/2. > > This means that interrupts that occur directly after the irq handler is > installed will be handled on a normal scheduling priority instead of the > realtime priority that you would expect. Fixed this by setting the RT > priority on creation of the irq_thread. > > Signed-off-by: Ivo Sieben <meltedpianoman@xxxxxxxxx> > --- > > RFC: > Whas there a specific reason for the irq_thread to be created on normal > scheduling and only set to RT priority when woken up? No. > This patch solves an issue for me where a device driver is expected to handle an > interrupt immediatly after irq handlers are installed and interrupts enabled. You miss to explain what kind of issue that is. 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
