Home
last modified time | relevance | path

Searched refs:hardirq (Results 1 – 21 of 21) sorted by relevance

/linux-4.4.14/Documentation/locking/
Dlockdep-design.txt38 - 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.
[all …]
/linux-4.4.14/Documentation/DocBook/
Dgenericirq.xml.db21 API-synchronize-hardirq
27 API-disable-hardirq
Dkernel-api.xml.db363 API-synchronize-hardirq
369 API-disable-hardirq
/linux-4.4.14/arch/um/include/asm/
DKbuild12 generic-y += hardirq.h
/linux-4.4.14/arch/xtensa/include/asm/
DKbuild10 generic-y += hardirq.h
/linux-4.4.14/drivers/sh/intc/
DKconfig13 This enables support for hardware-assisted userspace hardirq
/linux-4.4.14/arch/cris/include/asm/
DKbuild15 generic-y += hardirq.h
/linux-4.4.14/arch/arc/include/asm/
DKbuild13 generic-y += hardirq.h
/linux-4.4.14/arch/hexagon/include/asm/
DKbuild18 generic-y += hardirq.h
/linux-4.4.14/arch/metag/include/asm/
DKbuild15 generic-y += hardirq.h
/linux-4.4.14/arch/unicore32/include/asm/
DKbuild18 generic-y += hardirq.h
/linux-4.4.14/arch/nios2/include/asm/
DKbuild21 generic-y += hardirq.h
/linux-4.4.14/arch/openrisc/include/asm/
DKbuild27 generic-y += hardirq.h
/linux-4.4.14/kernel/trace/
Dtrace_output.c390 int hardirq; in trace_print_lat_fmt() local
393 hardirq = entry->flags & TRACE_FLAG_HARDIRQ; in trace_print_lat_fmt()
418 (hardirq && softirq) ? 'H' : in trace_print_lat_fmt()
419 hardirq ? 'h' : in trace_print_lat_fmt()
/linux-4.4.14/arch/h8300/include/asm/
DKbuild21 generic-y += hardirq.h
/linux-4.4.14/Documentation/
Dirqflags-tracing.txt5 the "irq-flags tracing" feature "traces" hardirq and softirq state, in
/linux-4.4.14/Documentation/trace/
Dftrace.txt569 # | / _---=> hardirq/softirq
622 # || / _---=> hardirq/softirq
680 hardirq/softirq:
953 # || / _---=> hardirq/softirq
1004 # || / _---=> hardirq/softirq
1099 # || / _---=> hardirq/softirq
1136 # || / _---=> hardirq/softirq
1249 # || / _---=> hardirq/softirq
1302 # || / _---=> hardirq/softirq
1415 # || / _---=> hardirq/softirq
[all …]
/linux-4.4.14/Documentation/RCU/
DwhatisRCU.txt337 hardirq enter / hardirq exit
904 c. Do you need to treat NMI handlers, hardirq handlers,
/linux-4.4.14/tools/lib/traceevent/
Devent-parse.c5085 int hardirq; in pevent_data_lat_fmt() local
5113 hardirq = lat_flags & TRACE_FLAG_HARDIRQ; in pevent_data_lat_fmt()
5122 (hardirq && softirq) ? 'H' : in pevent_data_lat_fmt()
5123 hardirq ? 'h' : softirq ? 's' : '.'); in pevent_data_lat_fmt()
/linux-4.4.14/arch/
DKconfig498 in the end of an hardirq.
/linux-4.4.14/init/
DKconfig359 between system, softirq and hardirq state, so there is a
388 transitions between softirq and hardirq state, so there can be a