Searched refs:hardirq (Results 1 – 18 of 18) sorted by relevance
| /linux/arch/s390/kernel/ |
| H 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/ |
| H A 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 …]
|
| /linux/drivers/pci/hotplug/ |
| H A D | TODO | 10 hardirq handler cpqhp_ctrl_intr(). Convert this to threaded IRQ handling. 50 * The hardirq handler shpc_isr() queues events on a workqueue. It can be
|
| /linux/Documentation/translations/zh_CN/core-api/irq/ |
| H A D | irqflags-tracing.rst | 17 “irq-flags tracing”(中断标志追踪)功能可以 “追踪” hardirq和softirq的状态,它让
|
| /linux/drivers/sh/intc/ |
| H A D | Kconfig | 14 This enables support for hardware-assisted userspace hardirq
|
| /linux/Documentation/translations/it_IT/locking/ |
| H 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/ |
| H A D | Kbuild | 26 mandatory-y += hardirq.h
|
| /linux/Documentation/trace/ |
| H A D | eprobetrace.rst | 115 # | / _---=> hardirq/softirq 195 # | / _---=> hardirq/softirq 246 # | / _---=> hardirq/softirq
|
| H A D | ftrace.rst | 947 # | / _---=> hardirq/softirq 1000 # || / _---=> hardirq/softirq 1059 hardirq/softirq: 1060 - 'Z' - NMI occurred inside a hardirq 1517 # || / _---=> hardirq/softirq 1568 # || / _---=> hardirq/softirq 1645 # | / _---=> hardirq/softirq 1716 # || / _---=> hardirq/softirq 1754 # || / _---=> hardirq/softirq 1868 # || / _---=> hardirq/softirq [all …]
|
| H A D | timerlat-tracer.rst | 30 # | / _---=> hardirq/softirq 48 the *timer latency* observed at the *hardirq* context before the activation
|
| H A D | osnoise-tracer.rst | 61 # | / _---=> hardirq/softirq
|
| /linux/Documentation/core-api/irq/ |
| H A D | irqflags-tracing.rst | 7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
|
| /linux/kernel/trace/ |
| H A D | trace_output.c | 458 int hardirq; in trace_print_lat_fmt() local 464 hardirq = entry->flags & TRACE_FLAG_HARDIRQ; in trace_print_lat_fmt() 503 (nmi && hardirq) ? 'Z' : in trace_print_lat_fmt() 505 (hardirq && softirq) ? 'H' : in trace_print_lat_fmt() 506 hardirq ? 'h' : in trace_print_lat_fmt()
|
| H A D | Kconfig | 562 timer latency observed at the hardirq context before the
|
| /linux/Documentation/RCU/ |
| H A D | whatisRCU.rst | 416 hardirq enter / hardirq exit 1269 d. Do you need to treat NMI handlers, hardirq handlers,
|
| /linux/Documentation/admin-guide/pm/ |
| H A D | amd-pstate.rst | 521 # | / _---=> hardirq/softirq
|
| /linux/init/ |
| H A D | Kconfig | 565 between system, softirq and hardirq state, so there is a 597 transitions between softirq and hardirq state, so there can be a
|
| /linux/arch/ |
| H A D | Kconfig | 1150 in the end of an hardirq.
|