| /Linux-v5.4/Documentation/RCU/ |
| D | NMI-RCU.txt | 1 Using RCU to Protect Dynamic NMI Handlers
7 how to do this, drawing loosely from Zwane Mwaikambo's NMI-timer
19 The dummy_nmi_callback() function is a "dummy" NMI handler that does
21 the NMI handler to take the default machine-specific action.
26 NMI handler.
43 The do_nmi() function processes each NMI. It first disables preemption
45 count of NMIs. It then invokes the NMI handler stored in the nmi_callback
47 default_do_nmi() function to handle a machine-specific NMI. Finally,
60 Back to the discussion of NMI and RCU...
67 The set_nmi_callback() function registers an NMI handler. Note that any
[all …]
|
| /Linux-v5.4/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
|
| /Linux-v5.4/Documentation/trace/ |
| D | events-nmi.rst | 2 NMI Trace Events
14 NMI handlers are hogging large amounts of CPU time. The kernel
17 INFO: NMI handler took too long to run: 9.207 msecs
|
| /Linux-v5.4/arch/c6x/kernel/ |
| D | vectors.S | 63 IRQVEC NMI,_nmi_handler ; NMI interrupt
|
| /Linux-v5.4/Documentation/x86/ |
| 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 | 147 frequent performance monitoring non-maskable interrupts (see "NMI"
148 in /proc/interrupts). This exercises the NMI entry/exit code which
174 * Crashes at the first NMI. The NMI code is separate from main
176 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)
|
| D | mds.rst | 146 is when we return from a Non Maskable Interrupt (NMI), which is
149 (The reason that NMI is special is that prepare_exit_to_usermode() can
150 enable IRQs. In NMI context, NMIs are blocked, and we don't want to
|
| /Linux-v5.4/Documentation/admin-guide/sysctl/ |
| D | kernel.rst | 478 This parameter can be used to control the NMI watchdog
488 while a CPU is busy. Hence, the alternative name 'NMI watchdog'.
490 The NMI watchdog is disabled by default if the kernel is running as a guest
602 Controls the kernel's behavior when a CPU receives an NMI caused by
607 1: panic immediately. The IO error triggered an NMI. This indicates a
610 servers issue this sort of NMI when the dump button is pushed,
640 The default Linux behaviour on an NMI of either memory or unknown is
645 A small number of systems do generate NMI's for bizarre random reasons
1020 be issued an NMI and instructed to capture stack trace.
1023 NMI.
[all …]
|
| /Linux-v5.4/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-event_print.txt | 50 z : NMI context
51 Z : NMI context which triggered during hard
|
| /Linux-v5.4/drivers/char/mwave/ |
| D | 3780i.c | 408 rBootDomain.NMI = true; in dsp3780I_Reset()
443 rBootDomain.NMI = true; in dsp3780I_Run()
453 rBootDomain.NMI = false; in dsp3780I_Run()
|
| D | 3780i.h | 163 unsigned short NMI:1; /* RW: non maskable interrupt */ member
|
| /Linux-v5.4/Documentation/devicetree/bindings/interrupt-controller/ |
| D | renesas,rza1-irqc.txt | 7 - NMI edge select.
|
| D | ti,c64x+megamod-pic.txt | 7 C64X+ core. Priority 0 and 1 are used for reset and NMI respectively.
|
| /Linux-v5.4/Documentation/devicetree/bindings/mfd/ |
| D | ac100.txt | 13 - interrupts: SoC NMI / GPIO interrupt connected to the
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | lockup-watchdogs.rst | 42 task. An NMI perf event is generated every "watchdog_thresh"
46 'hardlockup detector' (the handler for the NMI perf event) will
|
| /Linux-v5.4/arch/x86/kernel/ |
| D | dumpstack_64.c | 81 EPAGERANGE(NMI),
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/firmware/ |
| D | sdei.txt | 7 a firmware-assisted NMI.
|
| /Linux-v5.4/arch/x86/ |
| D | Kconfig.debug | 236 bool "NMI Selftest"
239 Enabling this option turns on a quick NMI selftest to verify
240 that the NMI behaves correctly.
242 This might help diagnose strange hangs that rely on NMI to
|
| /Linux-v5.4/Documentation/ia64/ |
| D | mca.rst | 127 How is ia64 MCA/INIT different from x86 NMI?
129 * x86 NMI typically gets delivered to one cpu. MCA/INIT gets sent to
132 * x86 NMI cannot be nested. MCA/INIT can be nested, to a depth of 2
139 * x86 does not call the BIOS so the NMI handler does not have to worry
|
| /Linux-v5.4/arch/x86/mm/ |
| D | cpu_entry_area.c | 105 cea_map_stack(NMI); in percpu_setup_exception_stacks()
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| D | am335x-osd335x-common.dtsi | 60 interrupts = <7>; /* NMI */
|
| /Linux-v5.4/drivers/acpi/apei/ |
| D | Kconfig | 16 to the operating system. This improves NMI handling
|
| /Linux-v5.4/drivers/pinctrl/ |
| D | pinctrl-xway.c | 124 MFP_XWAY(GPIO8, GPIO, CGU, NMI, NONE),
262 GRP_MUX("nmi", NMI, pins_nmi),
488 MFP_XWAY(GPIO8, GPIO, CGU, NMI, MII),
594 GRP_MUX("nmi", NMI, danube_pins_nmi),
663 MFP_XWAY(GPIO8, GPIO, CGU, NMI, NONE),
802 GRP_MUX("nmi", NMI, xrx100_pins_nmi),
876 MFP_XWAY(GPIO8, GPIO, CGU, NMI, NONE),
1042 GRP_MUX("nmi", NMI, xrx200_pins_nmi),
|
| /Linux-v5.4/arch/nds32/kernel/ |
| D | ex-entry.S | 91 .long unhandled_exceptions !Reset/NMI
|
