Searched refs:hardirq (Results 1 – 21 of 21) sorted by relevance
| /Linux-v5.15/arch/s390/kernel/ |
| D | vtime.c | 127 u64 timer, clock, user, guest, system, hardirq, softirq; in do_account_vtime() local
158 hardirq = update_tsk_timer(&tsk->thread.hardirq_timer, in do_account_vtime()
163 clock - user - guest - system - hardirq - softirq; in do_account_vtime()
178 if (hardirq) in do_account_vtime()
179 account_system_index_scaled(tsk, hardirq, CPUTIME_IRQ); in do_account_vtime()
183 return virt_timer_forward(user + guest + system + hardirq + softirq); in do_account_vtime()
|
| /Linux-v5.15/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
167 If the read side section can be invoked from hardirq or softirq context,
|
| /Linux-v5.15/Documentation/translations/zh_CN/core-api/irq/ |
| D | irqflags-tracing.rst | 17 “irq-flags tracing”（中断标志追踪）功能可以 “追踪” hardirq和softirq的状态，它让
|
| /Linux-v5.15/drivers/pci/hotplug/ |
| D | TODO | 12 hardirq handler cpqhp_ctrl_intr(). Convert this to threaded IRQ handling.
69 * The hardirq handler shpc_isr() queues events on a workqueue. It can be
|
| /Linux-v5.15/drivers/sh/intc/ |
| D | Kconfig | 14 This enables support for hardware-assisted userspace hardirq
|
| /Linux-v5.15/include/asm-generic/ |
| D | Kbuild | 26 mandatory-y += hardirq.h
|
| /Linux-v5.15/kernel/trace/ |
| D | trace_output.c | 455 int hardirq; in trace_print_lat_fmt() local
460 hardirq = entry->flags & TRACE_FLAG_HARDIRQ; in trace_print_lat_fmt()
485 (nmi && hardirq) ? 'Z' : in trace_print_lat_fmt()
487 (hardirq && softirq) ? 'H' : in trace_print_lat_fmt()
488 hardirq ? 'h' : in trace_print_lat_fmt()
|
| D | Kconfig | 413 timer latency observed at the hardirq context before the
|
| /Linux-v5.15/Documentation/trace/ |
| D | timerlat-tracer.rst | 30 # | / _---=> hardirq/softirq
48 observed at the *hardirq* context before the activation of the thread.
|
| D | ftrace.rst | 854 # | / _---=> hardirq/softirq
907 # || / _---=> hardirq/softirq
965 hardirq/softirq:
966 - 'Z' - NMI occurred inside a hardirq
1379 # || / _---=> hardirq/softirq
1430 # || / _---=> hardirq/softirq
1507 # | / _---=> hardirq/softirq
1578 # || / _---=> hardirq/softirq
1616 # || / _---=> hardirq/softirq
1730 # || / _---=> hardirq/softirq
[all …]
|
| D | osnoise-tracer.rst | 61 # | / _---=> hardirq/softirq
|
| D | histogram.rst | 1195 # | / _---=> hardirq/softirq
|
| /Linux-v5.15/Documentation/core-api/irq/ |
| D | irqflags-tracing.rst | 7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
|
| /Linux-v5.15/Documentation/gpu/ |
| D | todo.rst | 490 main issue here is that panics can be triggered from hardirq contexts and
491 hence all panic related callback can run in hardirq context. It would be
493 e.g. trigger calls through drm debugfs files. hardirq context could be
507 even spinlocks (because NMI and hardirq can panic too). We need to either
|
| /Linux-v5.15/Documentation/RCU/ |
| D | whatisRCU.rst | 377 hardirq enter / hardirq exit
1011 c. Do you need to treat NMI handlers, hardirq handlers,
|
| /Linux-v5.15/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.15/init/ |
| D | Kconfig | 494 between system, softirq and hardirq state, so there is a
526 transitions between softirq and hardirq state, so there can be a
|
| /Linux-v5.15/arch/ |
| D | Kconfig | 884 in the end of an hardirq.
|
| /Linux-v5.15/Documentation/admin-guide/pm/ |
| D | intel_pstate.rst | 749 # | / _---=> hardirq/softirq
|
| /Linux-v5.15/Documentation/x86/ |
| D | resctrl.rst | 655 # | / _---=> hardirq/softirq
|
