Lines Matching refs:hardirq

38  - hardirq
68 A softirq-unsafe lock-class is automatically hardirq-unsafe as well. The
72  <hardirq-safe> and <hardirq-unsafe>
97    <hardirq-safe>   ->  <hardirq-unsafe>
100 The first rule comes from the fact the a hardirq-safe lock could be
101 taken by a hardirq context, interrupting a hardirq-unsafe lock - and
113 - if a new hardirq-safe lock is discovered, we check whether it
114   took any hardirq-unsafe lock in the past.
119 - if a new hardirq-unsafe lock is discovered, we check whether any
120   hardirq-safe lock took it in the past.
126 could interrupt _any_ of the irq-unsafe or hardirq-unsafe locks, which
196 every possible hardirq and softirq nesting scenario (which is impossible
202     even hardirq-disabled codepaths] are correct and do not interfere