| /Linux-v4.19/Documentation/locking/ |
| D | lockdep-design.txt | 39 - 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 that 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-v4.19/arch/s390/kernel/ |
| D | vtime.c | 127 u64 timer, clock, user, guest, system, hardirq, softirq, steal; in do_account_vtime() local
160 hardirq = update_tsk_timer(&tsk->thread.hardirq_timer, in do_account_vtime()
165 clock - user - guest - system - hardirq - softirq; in do_account_vtime()
180 if (hardirq) in do_account_vtime()
181 account_system_index_scaled(tsk, hardirq, CPUTIME_IRQ); in do_account_vtime()
191 return virt_timer_forward(user + guest + system + hardirq + softirq); in do_account_vtime()
|
| /Linux-v4.19/arch/um/include/asm/ |
| D | Kbuild | 13 generic-y += hardirq.h
|
| /Linux-v4.19/arch/arc/include/asm/ |
| D | Kbuild | 11 generic-y += hardirq.h
|
| /Linux-v4.19/arch/xtensa/include/asm/ |
| D | Kbuild | 11 generic-y += hardirq.h
|
| /Linux-v4.19/arch/microblaze/include/asm/ |
| D | Kbuild | 13 generic-y += hardirq.h
|
| /Linux-v4.19/arch/unicore32/include/asm/ |
| D | Kbuild | 13 generic-y += hardirq.h
|
| /Linux-v4.19/drivers/sh/intc/ |
| D | Kconfig | 13 This enables support for hardware-assisted userspace hardirq
|
| /Linux-v4.19/arch/hexagon/include/asm/ |
| D | Kbuild | 13 generic-y += hardirq.h
|
| /Linux-v4.19/arch/nios2/include/asm/ |
| D | Kbuild | 19 generic-y += hardirq.h
|
| /Linux-v4.19/arch/openrisc/include/asm/ |
| D | Kbuild | 16 generic-y += hardirq.h
|
| /Linux-v4.19/arch/h8300/include/asm/ |
| D | Kbuild | 19 generic-y += hardirq.h
|
| /Linux-v4.19/arch/nds32/include/asm/ |
| D | Kbuild | 26 generic-y += hardirq.h
|
| /Linux-v4.19/kernel/trace/ |
| D | trace_output.c | 452 int hardirq; in trace_print_lat_fmt() local
457 hardirq = entry->flags & TRACE_FLAG_HARDIRQ; in trace_print_lat_fmt()
482 (nmi && hardirq) ? 'Z' : in trace_print_lat_fmt()
484 (hardirq && softirq) ? 'H' : in trace_print_lat_fmt()
485 hardirq ? 'h' : in trace_print_lat_fmt()
|
| /Linux-v4.19/arch/riscv/include/asm/ |
| D | Kbuild | 17 generic-y += hardirq.h
|
| /Linux-v4.19/Documentation/ |
| D | irqflags-tracing.txt | 7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
|
| /Linux-v4.19/Documentation/trace/ |
| D | ftrace.rst | 781 # | / _---=> hardirq/softirq
834 # || / _---=> hardirq/softirq
892 hardirq/softirq:
893 - 'Z' - NMI occurred inside a hardirq
1290 # || / _---=> hardirq/softirq
1341 # || / _---=> hardirq/softirq
1437 # || / _---=> hardirq/softirq
1475 # || / _---=> hardirq/softirq
1589 # || / _---=> hardirq/softirq
1642 # || / _---=> hardirq/softirq
[all …]
|
| D | histogram.rst | 1206 # | / _---=> hardirq/softirq
|
| /Linux-v4.19/Documentation/gpu/ |
| D | todo.rst | 307 main issue here is that panics can be triggered from hardirq contexts and
308 hence all panic related callback can run in hardirq context. It would be
310 e.g. trigger calls through drm debugfs files. hardirq context could be
324 even spinlocks (because NMI and hardirq can panic too). We need to either
|
| /Linux-v4.19/Documentation/RCU/ |
| D | whatisRCU.txt | 342 hardirq enter / hardirq exit
928 c. Do you need to treat NMI handlers, hardirq handlers,
|
| /Linux-v4.19/tools/lib/traceevent/ |
| D | event-parse.c | 5149 int hardirq; in tep_data_lat_fmt() local
5177 hardirq = lat_flags & TRACE_FLAG_HARDIRQ; in tep_data_lat_fmt()
5186 (hardirq && softirq) ? 'H' : in tep_data_lat_fmt()
5187 hardirq ? 'h' : softirq ? 's' : '.'); in tep_data_lat_fmt()
|
| /Linux-v4.19/arch/ |
| D | Kconfig | 558 in the end of an hardirq.
|
| /Linux-v4.19/init/ |
| D | Kconfig | 382 between system, softirq and hardirq state, so there is a
413 transitions between softirq and hardirq state, so there can be a
|
| /Linux-v4.19/Documentation/admin-guide/pm/ |
| D | intel_pstate.rst | 705 # | / _---=> hardirq/softirq
|
| /Linux-v4.19/Documentation/x86/ |
| D | intel_rdt_ui.txt | 583 # | / _---=> hardirq/softirq
|
