| /openbmc/linux/arch/s390/kernel/ |
| H A 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()
|
| /openbmc/linux/Documentation/locking/ |
| H 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 …]
|
| H 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,
|
| /openbmc/linux/Documentation/translations/zh_CN/core-api/irq/ |
| H A D | irqflags-tracing.rst | 17 “irq-flags tracing”（中断标志追踪）功能可以 “追踪” hardirq和softirq的状态，它让
|
| /openbmc/linux/drivers/pci/hotplug/ |
| H A D | TODO | 12 hardirq handler cpqhp_ctrl_intr(). Convert this to threaded IRQ handling.
61 * The hardirq handler shpc_isr() queues events on a workqueue. It can be
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/pm-graph/pm-graph/ |
| H A D | 0001-sleepgraph-add-support-for-RT-kernel-ftrace-flags.patch | 12 || / _---=> hardirq/softirq
|
| /openbmc/linux/drivers/sh/intc/ |
| H A D | Kconfig | 14 This enables support for hardware-assisted userspace hardirq
|
| /openbmc/linux/include/asm-generic/ |
| H A D | Kbuild | 27 mandatory-y += hardirq.h
|
| /openbmc/linux/Documentation/core-api/irq/ |
| H A D | irqflags-tracing.rst | 7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
|
| /openbmc/linux/kernel/trace/ |
| H 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()
|
| H A D | Kconfig | 491 timer latency observed at the hardirq context before the
|
| /openbmc/linux/Documentation/trace/ |
| H A D | ftrace.rst | 950 # || / _---=> hardirq/softirq
1008 hardirq/softirq:
1009 - 'Z' - NMI occurred inside a hardirq
1441 # || / _---=> hardirq/softirq
1492 # || / _---=> hardirq/softirq
1640 # || / _---=> hardirq/softirq
1678 # || / _---=> hardirq/softirq
1792 # || / _---=> hardirq/softirq
1845 # || / _---=> hardirq/softirq
1958 # || / _---=> hardirq/softirq
[all …]
|
| H A D | timerlat-tracer.rst | 30 # | / _---=> hardirq/softirq
48 observed at the *hardirq* context before the activation of the thread.
|
| H A D | osnoise-tracer.rst | 61 # | / _---=> hardirq/softirq
|
| H A D | histogram.rst | 1204 # | / _---=> hardirq/softirq
1963 # | / _---=> hardirq/softirq
|
| /openbmc/linux/Documentation/gpu/ |
| H A D | todo.rst | 497 main issue here is that panics can be triggered from hardirq contexts and
498 hence all panic related callback can run in hardirq context. It would be
500 e.g. trigger calls through drm debugfs files. hardirq context could be
518 even spinlocks (because NMI and hardirq can panic too). We need to either
|
| /openbmc/linux/Documentation/RCU/ |
| H A D | whatisRCU.rst | 394 hardirq enter / hardirq exit
1148 d. Do you need to treat NMI handlers, hardirq handlers,
|
| /openbmc/linux/Documentation/admin-guide/pm/ |
| H A D | amd-pstate.rst | 439 # | / _---=> hardirq/softirq
|
| H A D | intel_pstate.rst | 749 # | / _---=> hardirq/softirq
|
| /openbmc/linux/init/ |
| H A D | Kconfig | 508 between system, softirq and hardirq state, so there is a
540 transitions between softirq and hardirq state, so there can be a
|
| /openbmc/linux/arch/ |
| H A D | Kconfig | 985 in the end of an hardirq.
|
| /openbmc/openbmc/poky/documentation/profile-manual/ |
| H A D | usage.rst | 1275 # | / _---=> hardirq/softirq
1608 # | / _---=> hardirq/softirq
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | resctrl.rst | 805 # | / _---=> hardirq/softirq
|