Lines Matching refs:hardirq

52 - hardirq
87                          | \---> hardirq disabled and not in hardirq context
88                           \----> acquired in hardirq context
117 A softirq-unsafe lock-class is automatically hardirq-unsafe as well. The
121  <hardirq-safe> or <hardirq-unsafe>
156    <hardirq-safe>   ->  <hardirq-unsafe>
159 The first rule comes from the fact that a hardirq-safe lock could be
160 taken by a hardirq context, interrupting a hardirq-unsafe lock - and
172 - if a new hardirq-safe lock is discovered, we check whether it
173   took any hardirq-unsafe lock in the past.
178 - if a new hardirq-unsafe lock is discovered, we check whether any
179   hardirq-safe lock took it in the past.
185 could interrupt _any_ of the irq-unsafe or hardirq-unsafe locks, which
302 every possible hardirq and softirq nesting scenario (which is impossible
310     even hardirq-disabled codepaths] are correct and do not interfere