Searched refs:hardirq (Results 1 – 18 of 18) sorted by relevance
38 - hardirq68 A softirq-unsafe lock-class is automatically hardirq-unsafe as well. The72 <hardirq-safe> and <hardirq-unsafe>97 <hardirq-safe> -> <hardirq-unsafe>100 The first rule comes from the fact the a hardirq-safe lock could be101 taken by a hardirq context, interrupting a hardirq-unsafe lock - and113 - if a new hardirq-safe lock is discovered, we check whether it114 took any hardirq-unsafe lock in the past.119 - if a new hardirq-unsafe lock is discovered, we check whether any120 hardirq-safe lock took it in the past.[all …]
12 generic-y += hardirq.h
11 generic-y += hardirq.h
13 This enables support for hardware-assisted userspace hardirq
14 generic-y += hardirq.h
15 generic-y += hardirq.h
18 generic-y += hardirq.h
21 generic-y += hardirq.h
27 generic-y += hardirq.h
434 int hardirq; in trace_print_lat_fmt() local437 hardirq = entry->flags & TRACE_FLAG_HARDIRQ; in trace_print_lat_fmt()462 (hardirq && softirq) ? 'H' : in trace_print_lat_fmt()463 hardirq ? 'h' : in trace_print_lat_fmt()
5 the "irq-flags tracing" feature "traces" hardirq and softirq state, in
558 # | / _---=> hardirq/softirq611 # || / _---=> hardirq/softirq 669 hardirq/softirq:940 # || / _---=> hardirq/softirq 991 # || / _---=> hardirq/softirq 1086 # || / _---=> hardirq/softirq 1123 # || / _---=> hardirq/softirq 1236 # || / _---=> hardirq/softirq 1289 # || / _---=> hardirq/softirq 1402 # || / _---=> hardirq/softirq [all …]
335 hardirq enter / hardirq exit904 c. Do you need to treat NMI handlers, hardirq handlers,
4958 int hardirq; in pevent_data_lat_fmt() local4986 hardirq = lat_flags & TRACE_FLAG_HARDIRQ; in pevent_data_lat_fmt()4995 (hardirq && softirq) ? 'H' : in pevent_data_lat_fmt()4996 hardirq ? 'h' : softirq ? 's' : '.'); in pevent_data_lat_fmt()
486 in the end of an hardirq.
359 between system, softirq and hardirq state, so there is a388 transitions between softirq and hardirq state, so there can be a