Searched refs:hardirq (Results 1 – 22 of 22) sorted by relevance
| /linux-5.19.10/arch/s390/kernel/ |
| D | vtime.c | 127 u64 timer, clock, user, guest, system, hardirq, softirq; in do_account_vtime() local
157 hardirq = update_tsk_timer(&tsk->thread.hardirq_timer, in do_account_vtime()
162 clock - user - guest - system - hardirq - softirq; in do_account_vtime()
177 if (hardirq) in do_account_vtime()
178 account_system_index_scaled(tsk, hardirq, CPUTIME_IRQ); in do_account_vtime()
182 return virt_timer_forward(user + guest + system + hardirq + softirq); in do_account_vtime()
|
| /linux-5.19.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
167 If the read side section can be invoked from hardirq or softirq context,
|
| /linux-5.19.10/Documentation/translations/zh_CN/core-api/irq/ |
| D | irqflags-tracing.rst | 17 “irq-flags tracing”（中断标志追踪）功能可以 “追踪” hardirq和softirq的状态，它让
|
| /linux-5.19.10/drivers/pci/hotplug/ |
| D | TODO | 12 hardirq handler cpqhp_ctrl_intr(). Convert this to threaded IRQ handling.
64 * The hardirq handler shpc_isr() queues events on a workqueue. It can be
|
| /linux-5.19.10/drivers/sh/intc/ |
| D | Kconfig | 14 This enables support for hardware-assisted userspace hardirq
|
| /linux-5.19.10/include/asm-generic/ |
| D | Kbuild | 26 mandatory-y += hardirq.h
|
| /linux-5.19.10/kernel/trace/ |
| D | trace_output.c | 446 int hardirq; in trace_print_lat_fmt() local
452 hardirq = entry->flags & TRACE_FLAG_HARDIRQ; in trace_print_lat_fmt()
480 (nmi && hardirq) ? 'Z' : in trace_print_lat_fmt()
482 (hardirq && softirq) ? 'H' : in trace_print_lat_fmt()
483 hardirq ? 'h' : in trace_print_lat_fmt()
|
| D | Kconfig | 454 timer latency observed at the hardirq context before the
|
| /linux-5.19.10/Documentation/trace/ |
| D | timerlat-tracer.rst | 30 # | / _---=> hardirq/softirq
48 observed at the *hardirq* context before the activation of the thread.
|
| D | ftrace.rst | 866 # | / _---=> hardirq/softirq
919 # || / _---=> hardirq/softirq
977 hardirq/softirq:
978 - 'Z' - NMI occurred inside a hardirq
1391 # || / _---=> hardirq/softirq
1442 # || / _---=> hardirq/softirq
1519 # | / _---=> hardirq/softirq
1590 # || / _---=> hardirq/softirq
1628 # || / _---=> hardirq/softirq
1742 # || / _---=> hardirq/softirq
[all …]
|
| D | osnoise-tracer.rst | 61 # | / _---=> hardirq/softirq
|
| D | histogram.rst | 1195 # | / _---=> hardirq/softirq
|
| /linux-5.19.10/Documentation/core-api/irq/ |
| D | irqflags-tracing.rst | 7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
|
| /linux-5.19.10/Documentation/gpu/ |
| D | todo.rst | 493 main issue here is that panics can be triggered from hardirq contexts and
494 hence all panic related callback can run in hardirq context. It would be
496 e.g. trigger calls through drm debugfs files. hardirq context could be
514 even spinlocks (because NMI and hardirq can panic too). We need to either
|
| /linux-5.19.10/Documentation/RCU/ |
| D | whatisRCU.rst | 379 hardirq enter / hardirq exit
1083 c. Do you need to treat NMI handlers, hardirq handlers,
|
| /linux-5.19.10/Documentation/admin-guide/pm/ |
| D | amd-pstate.rst | 353 # | / _---=> hardirq/softirq
|
| D | intel_pstate.rst | 749 # | / _---=> hardirq/softirq
|
| /linux-5.19.10/tools/lib/traceevent/ |
| D | event-parse.c | 5777 int hardirq; in data_latency_format() local
5806 hardirq = lat_flags & TRACE_FLAG_HARDIRQ; in data_latency_format()
5815 (hardirq && softirq) ? 'H' : in data_latency_format()
5816 hardirq ? 'h' : softirq ? 's' : '.'); in data_latency_format()
|
| /linux-5.19.10/init/ |
| D | Kconfig | 490 between system, softirq and hardirq state, so there is a
522 transitions between softirq and hardirq state, so there can be a
|
| /linux-5.19.10/arch/ |
| D | Kconfig | 917 in the end of an hardirq.
|
| /linux-5.19.10/Documentation/x86/ |
| D | resctrl.rst | 655 # | / _---=> hardirq/softirq
|