Lines Matching refs:hardirq

54 - hardirq
90                          | \---> hardirq disabled and not in hardirq context
91                           \----> acquired in hardirq context
120 A softirq-unsafe lock-class is automatically hardirq-unsafe as well. The
124  <hardirq-safe> or <hardirq-unsafe>
159    <hardirq-safe>   ->  <hardirq-unsafe>
162 The first rule comes from the fact that a hardirq-safe lock could be
163 taken by a hardirq context, interrupting a hardirq-unsafe lock - and
175 - if a new hardirq-safe lock is discovered, we check whether it
176   took any hardirq-unsafe lock in the past.
181 - if a new hardirq-unsafe lock is discovered, we check whether any
182   hardirq-safe lock took it in the past.
188 could interrupt _any_ of the irq-unsafe or hardirq-unsafe locks, which
305 every possible hardirq and softirq nesting scenario (which is impossible
313     even hardirq-disabled codepaths] are correct and do not interfere