| /linux-6.15/Documentation/RCU/ |
| H A 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::
63 Back to the discussion of NMI and RCU::
81 This function unregisters an NMI handler, restoring the original
82 dummy_nmi_handler(). However, there may well be an NMI handler
110 initialized some data that is to be used by the new NMI
112 be needed, because otherwise a CPU that received an NMI
[all …]
|
| H A D | index.rst | 24 NMI-RCU
|
| /linux-6.15/Documentation/watchdog/ |
| H A 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-6.15/Documentation/tools/rtla/ |
| H A 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
|
| H A D | rtla-osnoise-top.rst | 44 …ime Noise % CPU Aval Max Noise Max Single HW NMI IRQ S…
|
| /linux-6.15/Documentation/core-api/ |
| H A 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
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
|
| /linux-6.15/Documentation/trace/ |
| H A 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
|
| H A 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.
|
| /linux-6.15/Documentation/devicetree/bindings/interrupt-controller/ |
| H A 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
|
| H A D | allwinner,sun6i-a31-r-intc.yaml | 7 title: Allwinner A31 NMI/Wakeup Interrupt Controller
41 The GIC interrupt labeled as "External NMI".
|
| H A D | renesas,rzv2h-icu.yaml | 17 The Interrupt Control Unit (ICU) handles external interrupts (NMI, IRQ, and
28 description: The first cell is the SPI number of the NMI or the
44 - description: NMI interrupt
|
| H A D | renesas,rza1-irqc.yaml | 17 - NMI edge select.
|
| /linux-6.15/Documentation/translations/zh_TW/admin-guide/ |
| H A D | lockup-watchdogs.rst | 37 Hrtimer用於週期性產生中斷並喚醒watchdog線程；NMI perf事件則以”watchdog_thresh“
40 斷髮生，'hardlockup 檢測器'(即NMI perf事件處理函數)將會視系統配置而選擇產生內核
|
| /linux-6.15/Documentation/translations/zh_CN/admin-guide/ |
| H A D | lockup-watchdogs.rst | 37 Hrtimer用于周期性产生中断并唤醒watchdog线程；NMI perf事件则以”watchdog_thresh“
40 断发生，'hardlockup 检测器'(即NMI perf事件处理函数)将会视系统配置而选择产生内核
|
| /linux-6.15/Documentation/arch/x86/ |
| H A 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
|
| H A 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
|
| H A 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
|
| /linux-6.15/Documentation/arch/x86/x86_64/ |
| H A 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.
|
| /linux-6.15/arch/x86/kernel/ |
| H A D | fred.c | 90 wrmsrl(MSR_IA32_FRED_RSP2, __this_cpu_ist_top_va(NMI)); in cpu_init_fred_rsps()
|
| H A D | dumpstack_64.c | 87 EPAGERANGE(NMI),
|
| /linux-6.15/Documentation/admin-guide/sysctl/ |
| H A D | kernel.rst | 667 This parameter can be used to control the NMI watchdog
678 while a CPU is busy. Hence, the alternative name 'NMI watchdog'.
817 Controls the kernel's behavior when a CPU receives an NMI caused by
822 1 Panic immediately. The IO error triggered an NMI. This indicates a
825 servers issue this sort of NMI when the dump button is pushed,
1398 be issued an NMI and instructed to capture stack trace.
1401 NMI.
1612 The value in this file affects behavior of handling NMI. When the
1616 NMI switch that most IA32 servers have fires unknown NMI up, for
1617 example. If a system hangs up, try pressing the NMI switch.
[all …]
|
| /linux-6.15/drivers/char/mwave/ |
| H A D | 3780i.c | 408 rBootDomain.NMI = true; in dsp3780I_Reset()
443 rBootDomain.NMI = true; in dsp3780I_Run()
453 rBootDomain.NMI = false; in dsp3780I_Run()
|
| /linux-6.15/arch/x86/ |
| H A D | Kconfig.debug | 177 bool "NMI Selftest"
180 Enabling this option turns on a quick NMI selftest to verify
181 that the NMI behaves correctly.
183 This might help diagnose strange hangs that rely on NMI to
|
| /linux-6.15/Documentation/admin-guide/ |
| H A 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
|
| /linux-6.15/Documentation/devicetree/bindings/arm/firmware/ |
| H A D | sdei.txt | 7 a firmware-assisted NMI.
|