| /Linux-v5.4/Documentation/locking/ |
| D | lockdep-design.rst | 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.
[all …]
|
| /Linux-v5.4/arch/s390/kernel/ |
| D | vtime.c | 127 u64 timer, clock, user, guest, system, hardirq, softirq; 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()
185 return virt_timer_forward(user + guest + system + hardirq + softirq); in do_account_vtime()
|
| /Linux-v5.4/drivers/pci/hotplug/ |
| D | TODO | 12 hardirq handler cpqhp_ctrl_intr(). Convert this to threaded IRQ handling.
72 * The hardirq handler shpc_isr() queues events on a workqueue. It can be
|
| /Linux-v5.4/arch/arc/include/asm/ |
| D | Kbuild | 10 generic-y += hardirq.h
|
| /Linux-v5.4/arch/xtensa/include/asm/ |
| D | Kbuild | 13 generic-y += hardirq.h
|
| /Linux-v5.4/arch/riscv/include/asm/ |
| D | Kbuild | 15 generic-y += hardirq.h
|
| /Linux-v5.4/arch/microblaze/include/asm/ |
| D | Kbuild | 15 generic-y += hardirq.h
|
| /Linux-v5.4/arch/hexagon/include/asm/ |
| D | Kbuild | 14 generic-y += hardirq.h
|
| /Linux-v5.4/drivers/sh/intc/ |
| D | Kconfig | 14 This enables support for hardware-assisted userspace hardirq
|
| /Linux-v5.4/arch/unicore32/include/asm/ |
| D | Kbuild | 15 generic-y += hardirq.h
|
| /Linux-v5.4/arch/nios2/include/asm/ |
| D | Kbuild | 20 generic-y += hardirq.h
|
| /Linux-v5.4/arch/openrisc/include/asm/ |
| D | Kbuild | 17 generic-y += hardirq.h
|
| /Linux-v5.4/arch/nds32/include/asm/ |
| D | Kbuild | 19 generic-y += hardirq.h
|
| /Linux-v5.4/arch/csky/include/asm/ |
| D | Kbuild | 17 generic-y += hardirq.h
|
| /Linux-v5.4/arch/h8300/include/asm/ |
| D | Kbuild | 20 generic-y += hardirq.h
|
| /Linux-v5.4/kernel/trace/ |
| D | trace_output.c | 430 int hardirq; in trace_print_lat_fmt() local
435 hardirq = entry->flags & TRACE_FLAG_HARDIRQ; in trace_print_lat_fmt()
460 (nmi && hardirq) ? 'Z' : in trace_print_lat_fmt()
462 (hardirq && softirq) ? 'H' : in trace_print_lat_fmt()
463 hardirq ? 'h' : in trace_print_lat_fmt()
|
| /Linux-v5.4/Documentation/ |
| D | irqflags-tracing.txt | 7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
|
| /Linux-v5.4/Documentation/trace/ |
| D | ftrace.rst | 820 # | / _---=> hardirq/softirq
873 # || / _---=> hardirq/softirq
931 hardirq/softirq:
932 - 'Z' - NMI occurred inside a hardirq
1329 # || / _---=> hardirq/softirq
1380 # || / _---=> hardirq/softirq
1457 # | / _---=> hardirq/softirq
1528 # || / _---=> hardirq/softirq
1566 # || / _---=> hardirq/softirq
1680 # || / _---=> hardirq/softirq
[all …]
|
| /Linux-v5.4/Documentation/gpu/ |
| D | todo.rst | 308 main issue here is that panics can be triggered from hardirq contexts and
309 hence all panic related callback can run in hardirq context. It would be
311 e.g. trigger calls through drm debugfs files. hardirq context could be
325 even spinlocks (because NMI and hardirq can panic too). We need to either
|
| /Linux-v5.4/Documentation/RCU/ |
| D | whatisRCU.txt | 354 hardirq enter / hardirq exit
942 c. Do you need to treat NMI handlers, hardirq handlers,
|
| /Linux-v5.4/tools/lib/traceevent/ |
| D | event-parse.c | 5232 int hardirq; in data_latency_format() local
5261 hardirq = lat_flags & TRACE_FLAG_HARDIRQ; in data_latency_format()
5270 (hardirq && softirq) ? 'H' : in data_latency_format()
5271 hardirq ? 'h' : softirq ? 's' : '.'); in data_latency_format()
|
| /Linux-v5.4/arch/ |
| D | Kconfig | 613 in the end of an hardirq.
|
| /Linux-v5.4/init/ |
| D | Kconfig | 431 between system, softirq and hardirq state, so there is a
463 transitions between softirq and hardirq state, so there can be a
|
| /Linux-v5.4/Documentation/admin-guide/pm/ |
| D | intel_pstate.rst | 722 # | / _---=> hardirq/softirq
|
| /Linux-v5.4/Documentation/x86/ |
| D | resctrl_ui.rst | 641 # | / _---=> hardirq/softirq
|
