Searched refs:hardirq (Results 1 – 17 of 17) sorted by relevance
| /Linux-v5.10/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.10/Documentation/locking/ |
| D | lockdep-design.rst | 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.
[all …]
|
| D | seqlock.rst | 48 write side section. If the read section can be invoked from hardirq or
168 If the read side section can be invoked from hardirq or softirq context,
|
| /Linux-v5.10/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.10/drivers/sh/intc/ |
| D | Kconfig | 14 This enables support for hardware-assisted userspace hardirq
|
| /Linux-v5.10/kernel/trace/ |
| D | trace_output.c | 445 int hardirq; in trace_print_lat_fmt() local
450 hardirq = entry->flags & TRACE_FLAG_HARDIRQ; in trace_print_lat_fmt()
475 (nmi && hardirq) ? 'Z' : in trace_print_lat_fmt()
477 (hardirq && softirq) ? 'H' : in trace_print_lat_fmt()
478 hardirq ? 'h' : in trace_print_lat_fmt()
|
| /Linux-v5.10/include/asm-generic/ |
| D | Kbuild | 26 mandatory-y += hardirq.h
|
| /Linux-v5.10/Documentation/core-api/irq/ |
| D | irqflags-tracing.rst | 7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
|
| /Linux-v5.10/Documentation/trace/ |
| D | ftrace.rst | 854 # | / _---=> hardirq/softirq
907 # || / _---=> hardirq/softirq
965 hardirq/softirq:
966 - 'Z' - NMI occurred inside a hardirq
1373 # || / _---=> hardirq/softirq
1424 # || / _---=> hardirq/softirq
1501 # | / _---=> hardirq/softirq
1572 # || / _---=> hardirq/softirq
1610 # || / _---=> hardirq/softirq
1724 # || / _---=> hardirq/softirq
[all …]
|
| D | histogram.rst | 1194 # | / _---=> hardirq/softirq
|
| /Linux-v5.10/Documentation/gpu/ |
| D | todo.rst | 462 main issue here is that panics can be triggered from hardirq contexts and
463 hence all panic related callback can run in hardirq context. It would be
465 e.g. trigger calls through drm debugfs files. hardirq context could be
479 even spinlocks (because NMI and hardirq can panic too). We need to either
|
| /Linux-v5.10/Documentation/RCU/ |
| D | whatisRCU.rst | 377 hardirq enter / hardirq exit
1012 c. Do you need to treat NMI handlers, hardirq handlers,
|
| /Linux-v5.10/tools/lib/traceevent/ |
| D | event-parse.c | 5758 int hardirq; in data_latency_format() local
5787 hardirq = lat_flags & TRACE_FLAG_HARDIRQ; in data_latency_format()
5796 (hardirq && softirq) ? 'H' : in data_latency_format()
5797 hardirq ? 'h' : softirq ? 's' : '.'); in data_latency_format()
|
| /Linux-v5.10/arch/ |
| D | Kconfig | 696 in the end of an hardirq.
|
| /Linux-v5.10/init/ |
| D | Kconfig | 469 between system, softirq and hardirq state, so there is a
501 transitions between softirq and hardirq state, so there can be a
|
| /Linux-v5.10/Documentation/admin-guide/pm/ |
| D | intel_pstate.rst | 742 # | / _---=> hardirq/softirq
|
| /Linux-v5.10/Documentation/x86/ |
| D | resctrl_ui.rst | 655 # | / _---=> hardirq/softirq
|
