Hi Sebastian, Thanks a lot for your quick reply. I agree with all your points, I had a comment about one of them: > > So basically my questions are: > > 1. Does hard in hard irq mean hardware interrupt or does it imply > > interrupt context? > > I would drop that hard part. It is an interrupt handler. It then can be > either threaded or not and it can be always threaded or sometimes. > hard is used to distinguish this kind of interrupts from the soft-irqs. > But with threaded interrupts, you do have a handler that wakes up the thread. In this case there are 2 handlers, one handler executes in interrupt context and wakes up the thread, and the other runs in the thread. In this case, the term "interrupt handler" is confusing since it isn't clear which handler we're referring to. "hard interrupt handler" is also confusing - since if hard means "hardware", then technically the thread is also a "hard interrupt handler" since the interrupt line is masked (forced threaded interrupts are also one shot) till the thread clears the interrupt reason. Thanks, Joel -- 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
