Searched refs:hardirq (Results 1 – 22 of 22) sorted by relevance
| /linux/arch/s390/kernel/ |
| A D | vtime.c | 120 u64 timer, clock, user, guest, system, hardirq, softirq; in do_account_vtime() local
151 hardirq = update_tsk_timer(&tsk->thread.hardirq_timer, in do_account_vtime()
156 clock - user - guest - system - hardirq - softirq; in do_account_vtime()
171 if (hardirq) in do_account_vtime()
172 account_system_index_scaled(tsk, hardirq, CPUTIME_IRQ); in do_account_vtime()
176 return virt_timer_forward(user + guest + system + hardirq + softirq); in do_account_vtime()
|
| /linux/Documentation/locking/ |
| A D | lockdep-design.rst | 54 - hardirq
90 | \---> hardirq disabled and not in hardirq context
91 \----> acquired in hardirq context
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.
181 - if a new hardirq-unsafe lock is discovered, we check whether any
[all …]
|
| A 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/drivers/pci/hotplug/ |
| A D | TODO | 14 hardirq handler cpqhp_ctrl_intr(). Convert this to threaded IRQ handling.
54 * The hardirq handler shpc_isr() queues events on a workqueue. It can be
|
| /linux/Documentation/translations/zh_CN/core-api/irq/ |
| A D | irqflags-tracing.rst | 17 “irq-flags tracing”（中断标志追踪）功能可以 “追踪” hardirq和softirq的状态，它让
|
| /linux/drivers/sh/intc/ |
| A D | Kconfig | 14 This enables support for hardware-assisted userspace hardirq
|
| /linux/Documentation/translations/it_IT/locking/ |
| A D | lockdep-design.rst | 52 - hardirq
86 | \---> hardirq disabilitati e fuori da un contesto di hardirq
87 \----> acquisito in un contesto di hardirq
117 Una classe softirq insicura è automaticamente insicura anche per hardirq. I
121 <hardirq-safe> o <hardirq-unsafe>
156 <hardirq-safe> -> <hardirq-unsafe>
306 e differenti scenari con hardirq e softirq e annidamenti vari (nella pratica,
|
| /linux/include/asm-generic/ |
| A D | Kbuild | 26 mandatory-y += hardirq.h
|
| /linux/kernel/trace/ |
| A D | trace_output.c | 449 int hardirq; in trace_print_lat_fmt() local
455 hardirq = entry->flags & TRACE_FLAG_HARDIRQ; in trace_print_lat_fmt()
483 (nmi && hardirq) ? 'Z' : in trace_print_lat_fmt()
485 (hardirq && softirq) ? 'H' : in trace_print_lat_fmt()
486 hardirq ? 'h' : in trace_print_lat_fmt()
|
| A D | Kconfig | 491 timer latency observed at the hardirq context before the
|
| /linux/Documentation/core-api/irq/ |
| A D | irqflags-tracing.rst | 7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
|
| /linux/Documentation/trace/ |
| A D | ftrace.rst | 986 # || / _---=> hardirq/softirq
1044 hardirq/softirq:
1045 - 'Z' - NMI occurred inside a hardirq
1489 # || / _---=> hardirq/softirq
1540 # || / _---=> hardirq/softirq
1688 # || / _---=> hardirq/softirq
1726 # || / _---=> hardirq/softirq
1840 # || / _---=> hardirq/softirq
1893 # || / _---=> hardirq/softirq
2006 # || / _---=> hardirq/softirq
[all …]
|
| A D | timerlat-tracer.rst | 30 # | / _---=> hardirq/softirq
48 observed at the *hardirq* context before the activation of the thread.
|
| A D | osnoise-tracer.rst | 61 # | / _---=> hardirq/softirq
|
| A D | histogram.rst | 1204 # | / _---=> hardirq/softirq
1963 # | / _---=> hardirq/softirq
|
| /linux/Documentation/gpu/ |
| A D | todo.rst | 527 main issue here is that panics can be triggered from hardirq contexts and
528 hence all panic related callback can run in hardirq context. It would be
530 e.g. trigger calls through drm debugfs files. hardirq context could be
548 even spinlocks (because NMI and hardirq can panic too). We need to either
|
| /linux/Documentation/RCU/ |
| A D | whatisRCU.rst | 413 hardirq enter / hardirq exit
1167 d. Do you need to treat NMI handlers, hardirq handlers,
|
| /linux/Documentation/admin-guide/pm/ |
| A D | amd-pstate.rst | 523 # | / _---=> hardirq/softirq
|
| A D | intel_pstate.rst | 749 # | / _---=> hardirq/softirq
|
| /linux/init/ |
| A D | Kconfig | 522 between system, softirq and hardirq state, so there is a
554 transitions between softirq and hardirq state, so there can be a
|
| /linux/arch/ |
| A D | Kconfig | 1033 in the end of an hardirq.
|
| /linux/Documentation/arch/x86/ |
| A D | resctrl.rst | 864 # | / _---=> hardirq/softirq
|
Completed in 67 milliseconds