Hi, Recently had a discussion with a colleague about hard vs soft irqs. We also discussed process vs interrupt context and I had some confusion about when to (and when not to use) the terms hard irq handler. Just to clarify and use the right terminology, I'd like to understand whether the "hard" in hard irq implies interrupt context? To further confuse the matter, with CONFIG_PREEMPT_RT_FULL, all IRQs previously executing in interrupt context are now threaded. Then in this scenario, is it Ok to still call these irq handlers as hard irq handlers or should they now be strictly called threaded interrupt handlers now that the same handlers are forced to execute in a thread? If the "hard" in hard irq means hardware interrupt, then it would make sense to still call them hardirq handlers even though they're now executing in process context? So basically my questions are: 1. Does hard in hard irq mean hardware interrupt or does it imply interrupt context? 2. Can the terms "hard irq handler" still be used with CONFIG_PREEMPT_RT_FULL? Thanks a lot, 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
