Lines Matching +full:non +full:- +full:maskable

2 IRQ-flags state tracing
7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
9 every hardirqs-off/hardirqs-on, softirqs-off/softirqs-on event that
15 CONFIG_PROVE_RWSEM_LOCKING will be offered on an architecture - these
20 category, because lots of lowlevel assembly code deal with irq-flags
21 state changes. But an architecture can be irq-flags-tracing enabled in a
22 rather straightforward and risk-free manner.
25 code-organizational changes first:
27 - add and enable TRACE_IRQFLAGS_SUPPORT in their arch level Kconfig file
30 irq-flags-tracing support:
32 - in lowlevel entry code add (build-conditional) calls to the
34   closely guards whether the 'real' irq-flags matches the 'virtual'
35   irq-flags state, and complains loudly (and turns itself off) if the
37   irq-flags-tracing is spent in this state: look at the lockdep
40   lockdep complaint in the irq-flags-tracing functions arch support is
42 - if the architecture has non-maskable interrupts then those need to be
43   excluded from the irq-tracing [and lock validation] mechanism via
46 In general there is no risk from having an incomplete irq-flags-tracing
49 should be no crashes due to irq-tracing bugs. (except if the assembly