Il 02/08/2013 17:24, Michael Schnell ha scritto:
On 08/02/2013 04:53 PM, Marco Stornelli wrote:
- how to assign an interrupt (e.g. a dedicated timer) to the
subsystem ?
Interrupt handler are kernel thread, so you can schedule your kernel
thread on your "normal" cpu.
Sorry. I don't understand.
The point I'd like to make is, that for really low latency stuff the ISR
needs to take place immediately when the hardware fires an interrupt.
As the Linux kernel will (for the SMP CPUs it handles) need to disable
interrupt in certain cases, it is essential that the "really low
latency" interrupt is assigned to the AMP cpu (that the Kernel will
never touch).
AFAIC, no latency for cpu "under affinity".
That would be great but it need the stuff described above.
In fact the interrupt would need to be assigned to the AMP cpu by some
hardware means (that I don't know anything about yet), and not be
"forwarded" in any way from some other cpu (which is managed by the
Kernel) and thus might be in a "interrupt disable state at some point in
time.
I don't know your hw so my consideration are really general. ISRs in rt
kernel doesn't exist or at least the only work is to wake up the kernel
thread for the management. The thing you can do is to move the kernel
thread for interrupt X where you want to manage it, or you can set a
specific scheduler policy. For example you can set a SCHED_FIFO with a
very high priority for your "really low latency" tasks. RT kernel does
the work for you :) You can see here: http://lwn.net/Articles/146861/
Marco
--
To unsubscribe from this list: send the line "unsubscribe linux-embedded" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
