I noticed that preempt-realtime-core.patch does this to hardirq.h: -#define in_irq() (hardirq_count()) -#define in_softirq() (softirq_count()) -#define in_interrupt() (irq_count()) +#define in_irq() (hardirq_count() || (current->flags & PF_HARDIRQ)) +#define in_softirq() (softirq_count() || (current->flags & PF_SOFTIRQ)) +#define in_interrupt() (irq_count()) I was thinking that in order to have better patch bisection for future hard/softirq segmentation, that this chunk would be better suited to live in preempt-irqs-core.patch (where PF_HARDIRQ is introduced). That would reduce the preempt-realtime-core.patch for hardirq.h to just one line, if we drop the whitespace shuffling in there at the same time. I can send diffs of the existing 26rt9 patches, but I'm not sure how useful folks would find diffs of diffs (if any at all.). Since it doesn't impact the actual code base of the resulting patched tree, the other option is to just ignore it for 26 but keep it in mind for the future. Paul. -- 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
