Searched full:nmi (Results 1 – 25 of 70) sorted by relevance
123
| /Documentation/RCU/ |
| D | NMI-RCU.rst | 3 Using RCU to Protect Dynamic NMI Handlers
10 how to do this, drawing loosely from Zwane Mwaikambo's NMI-timer
21 The dummy_nmi_callback() function is a "dummy" NMI handler that does
23 the NMI handler to take the default machine-specific action::
28 NMI handler::
45 The do_nmi() function processes each NMI. It first disables preemption
47 count of NMIs. It then invokes the NMI handler stored in the nmi_callback
49 default_do_nmi() function to handle a machine-specific NMI. Finally,
63 Back to the discussion of NMI and RCU::
70 The set_nmi_callback() function registers an NMI handler. Note that any
[all …]
|
| D | index.rst | 24 NMI-RCU
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | allwinner,sun7i-a20-sc-nmi.yaml | 4 $id: http://devicetree.org/schemas/interrupt-controller/allwinner,sun7i-a20-sc-nmi.yaml#
25 - const: allwinner,sun6i-a31-sc-nmi
27 - const: allwinner,sun7i-a20-sc-nmi
28 - const: allwinner,sun9i-a80-nmi
31 - allwinner,sun8i-v3s-nmi
32 - allwinner,sun50i-a100-nmi
33 - allwinner,sun50i-h616-nmi
34 - const: allwinner,sun9i-a80-nmi
56 compatible = "allwinner,sun7i-a20-sc-nmi";
|
| D | renesas,rzg2l-irqc.yaml | 15 interrupts of NMI, IRQ, and GPIOINT and the interrupts of the built-in peripheral
19 - NMI edge select (NMI is not treated as NMI exception and supports fall edge and
36 description: The first cell should contain a macro RZG2L_{NMI,IRQX} included in the
52 - description: NMI interrupt
104 - const: nmi
263 interrupt-names = "nmi",
|
| D | allwinner,sun6i-a31-r-intc.yaml | 7 title: Allwinner A31 NMI/Wakeup Interrupt Controller
41 The GIC interrupt labeled as "External NMI".
|
| D | renesas,rza1-irqc.yaml | 17 - NMI edge select.
|
| /Documentation/watchdog/ |
| D | hpwdt.rst | 2 HPE iLO NMI Watchdog Driver
11 The HPE iLO NMI Watchdog driver is a kernel module that provides basic
12 watchdog functionality and handler for the iLO "Generate NMI to System"
34 NMI is delivered to the system. Setting the value to
35 zero disables the pretimeout NMI.
42 kdumptimeout Minimum timeout in seconds to apply upon receipt of an NMI
53 Due to limitations in the iLO hardware, the NMI pretimeout if enabled,
58 Upon receipt of an NMI from the iLO, the hpwdt driver will initiate a
70 If the hpwdt does not receive the NMI associated with an expiring timer,
76 The HPE iLO NMI Watchdog Driver and documentation were originally developed
|
| /Documentation/trace/ |
| D | events-nmi.rst | 2 NMI Trace Events
7 /sys/kernel/tracing/events/nmi
14 NMI handlers are hogging large amounts of CPU time. The kernel
17 INFO: NMI handler took too long to run: 9.207 msecs
34 cd /sys/kernel/tracing/events/nmi/nmi_handler
|
| D | osnoise-tracer.rst | 21 NMI or in the hardware itself. At the end of the period, hwlatd enables
23 prints a NMI occurrence counter. If the output does not report NMI
25 the latency. The hwlat detects the NMI execution by observing
26 the entry and exit of a NMI.
34 interference. The interference counter for NMI, IRQs, SoftIRQs, and
65 … CPU# |||| TIMESTAMP IN US IN US AVAILABLE IN US HW NMI IRQ SIRQ THREAD
142 - osnoise:nmi_noise: noise from NMI, including the duration.
|
| D | index.rst | 21 events-nmi
|
| /Documentation/core-api/ |
| D | entry.rst | 16 exceptions`_, `NMI and NMI-like exceptions`_.
197 NMI and NMI-like exceptions
200 NMIs and NMI-like exceptions (machine checks, double faults, debug
209 NMIs and other NMI-like exceptions handle state transitions without
226 preemption count modification in the NMI entry/exit case must not be
233 noinstr void nmi(struct pt_regs *regs)
277 NMIs can happen in any context. For example, an NMI-like exception triggered
278 while handling an NMI. So NMI entry code has to be reentrant and state updates
|
| D | local_ops.rst | 36 coherent counters in NMI handlers. It is especially useful for tracing purposes
68 * This CPU can use local ops from any context (process, irq, softirq, nmi, ...)
|
| /Documentation/tools/rtla/ |
| D | rtla-hwnoise.rst | 48 …CPU Period Runtime Noise % CPU Aval Max Noise Max Single HW NMI
67 The *HW* and *NMI* columns show the total number of *hardware* and *NMI* noise
80 and disabling the TSC watchdog to remove the NMI (it is possible to identify
87 …CPU Period Runtime Noise % CPU Aval Max Noise Max Single HW NMI
|
| D | rtla-osnoise-top.rst | 44 …ime Noise % CPU Aval Max Noise Max Single HW NMI IRQ S…
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | lantiq,pinctrl-xway.txt | 57 spi_cs2, spi_cs3, spi_cs4, spi_cs5, spi_cs6, asc0, asc0 cts rts, stp, nmi,
62 spi, asc, cgu, jtag, exin, stp, gpt, nmi, pci, ebu, dfe
69 spi_cs6, asc0, asc0 cts rts, stp, nmi, gpt1, gpt2, gpt3, clkout0, clkout1,
74 spi, asc, cgu, exin, stp, gpt, nmi, pci, ebu, mdio, dfe
84 stp, nmi, gpt1, gpt2, gpt3, clkout0, clkout1, clkout2, clkout3, gnt1,
89 spi, usif, cgu, exin, stp, gpt, nmi, pci, ebu, mdio, dfe, gphy
|
| /Documentation/arch/x86/ |
| D | mds.rst | 149 which kernel data could be accessed after VERW e.g. via an NMI after
155 a case when an NMI is generated in kernel after the exit-to-user path
156 has cleared the buffers. This case is not handled and NMI returning to
159 1. It is rare to get an NMI after VERW, but before returning to userspace.
160 2. For an unprivileged user, there is no known way to make that NMI
164 4. The NMI in question occurs after a VERW, i.e. when user state is
166 is only the data that NMI touches, and that may or may not be of
|
| D | kernel-stacks.rst | 42 double fault or NMI, which makes it easier to handle these unusual
60 NMI. arch/x86_64/kernel/entry.S::paranoidentry adjusts the stack
79 Used for non-maskable interrupts (NMI).
81 NMI can be delivered at any time, including when the kernel is in the
82 middle of switching stacks. Using IST for NMI events avoids making
|
| D | pti.rst | 145 frequent performance monitoring non-maskable interrupts (see "NMI"
146 in /proc/interrupts). This exercises the NMI entry/exit code which
172 * Crashes at the first NMI. The NMI code is separate from main
174 normal interrupts. Also caused by incorrectly mapping NMI
|
| D | entry_64.rst | 94 But if we are in an NMI/MCE/DEBUG/whatever super-atomic entry context,
99 Therefore, super-atomic entries (except NMI, which is handled separately)
|
| /Documentation/arch/x86/x86_64/ |
| D | fred.rst | 61 FRED allows explicit unblock of NMI with new event return instructions
63 unblocks NMI, e.g., when an exception happens during NMI handling.
|
| /Documentation/admin-guide/ |
| D | lockup-watchdogs.rst | 42 job. An NMI perf event is generated every "watchdog_thresh"
46 'hardlockup detector' (the handler for the NMI perf event) will
|
| /Documentation/devicetree/bindings/arm/firmware/ |
| D | sdei.txt | 7 a firmware-assisted NMI.
|
| /Documentation/admin-guide/sysctl/ |
| D | kernel.rst | 396 If this option is set, the kernel will send an NMI to all CPUs to dump
669 This parameter can be used to control the NMI watchdog
680 while a CPU is busy. Hence, the alternative name 'NMI watchdog'.
682 The NMI watchdog is disabled by default if the kernel is running as a guest
694 Factor to apply to the NMI watchdog timeout (only when ``nmi_watchdog`` is
696 ``watchdog_thresh`` when calculating the NMI watchdog timeout during an
699 A value of 0 means no change. The default value is 200 meaning the NMI
748 If this option is set, the kernel will send an NMI to all CPUs to dump
819 Controls the kernel's behavior when a CPU receives an NMI caused by
824 1 Panic immediately. The IO error triggered an NMI. This indicates a
[all …]
|
| /Documentation/translations/zh_TW/admin-guide/ |
| D | lockup-watchdogs.rst | 37 Hrtimer用於週期性產生中斷並喚醒watchdog線程；NMI perf事件則以”watchdog_thresh“
|
| /Documentation/translations/zh_CN/admin-guide/ |
| D | lockup-watchdogs.rst | 37 Hrtimer用于周期性产生中断并唤醒watchdog线程；NMI perf事件则以”watchdog_thresh“
|
123