Lines Matching refs:in

5 the "irq-flags tracing" feature "traces" hardirq and softirq state, in
8 happens in the kernel.
14 are locking APIs that are not used in IRQ context. (the one exception
17 architecture support for this is certainly not in the "trivial"
19 state changes. But an architecture can be irq-flags-tracing enabled in a
25 - add and enable TRACE_IRQFLAGS_SUPPORT in their arch level Kconfig file
30 - in lowlevel entry code add (build-conditional) calls to the
35   irq-flags-tracing is spent in this state: look at the lockdep
38   lockdep complaint in the irq-flags-tracing functions arch support is
44 in general there is no risk from having an incomplete irq-flags-tracing
45 implementation in an architecture: lockdep will detect that and will