Home
last modified time | relevance | path

Searched refs:hardirq (Results 1 – 21 of 21) sorted by relevance

/linux-6.3-rc2/arch/s390/kernel/
A Dvtime.c127 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-6.3-rc2/Documentation/locking/
A Dlockdep-design.rst54 - 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 Dseqlock.rst48 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-6.3-rc2/drivers/pci/hotplug/
A DTODO12 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
/linux-6.3-rc2/Documentation/translations/zh_CN/core-api/irq/
A Dirqflags-tracing.rst17 “irq-flags tracing”(中断标志追踪)功能可以 “追踪” hardirq和softirq的状态,它让
/linux-6.3-rc2/drivers/sh/intc/
A DKconfig14 This enables support for hardware-assisted userspace hardirq
/linux-6.3-rc2/include/asm-generic/
A DKbuild27 mandatory-y += hardirq.h
/linux-6.3-rc2/kernel/trace/
A Dtrace_output.c446 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()
A DKconfig476 timer latency observed at the hardirq context before the
/linux-6.3-rc2/Documentation/trace/
A Dtimerlat-tracer.rst30 # | / _---=> hardirq/softirq
48 observed at the *hardirq* context before the activation of the thread.
A Dftrace.rst919 # || / _---=> hardirq/softirq
977 hardirq/softirq:
978 - 'Z' - NMI occurred inside a hardirq
1391 # || / _---=> hardirq/softirq
1442 # || / _---=> hardirq/softirq
1590 # || / _---=> hardirq/softirq
1628 # || / _---=> hardirq/softirq
1742 # || / _---=> hardirq/softirq
1795 # || / _---=> hardirq/softirq
1908 # || / _---=> hardirq/softirq
[all …]
A Dosnoise-tracer.rst61 # | / _---=> hardirq/softirq
A Dhistogram.rst1204 # | / _---=> hardirq/softirq
1963 # | / _---=> hardirq/softirq
/linux-6.3-rc2/Documentation/core-api/irq/
A Dirqflags-tracing.rst7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
/linux-6.3-rc2/Documentation/gpu/
A Dtodo.rst468 main issue here is that panics can be triggered from hardirq contexts and
469 hence all panic related callback can run in hardirq context. It would be
471 e.g. trigger calls through drm debugfs files. hardirq context could be
489 even spinlocks (because NMI and hardirq can panic too). We need to either
/linux-6.3-rc2/Documentation/RCU/
A DwhatisRCU.rst394 hardirq enter / hardirq exit
1149 d. Do you need to treat NMI handlers, hardirq handlers,
/linux-6.3-rc2/Documentation/admin-guide/pm/
A Damd-pstate.rst422 # | / _---=> hardirq/softirq
A Dintel_pstate.rst749 # | / _---=> hardirq/softirq
/linux-6.3-rc2/init/
A DKconfig499 between system, softirq and hardirq state, so there is a
531 transitions between softirq and hardirq state, so there can be a
/linux-6.3-rc2/arch/
A DKconfig924 in the end of an hardirq.
/linux-6.3-rc2/Documentation/x86/
A Dresctrl.rst798 # | / _---=> hardirq/softirq

Completed in 44 milliseconds