Home
last modified time | relevance | path

Searched refs:NMI (Results 1 – 25 of 93) sorted by relevance

1234

/linux-6.3-rc2/Documentation/RCU/
A DNMI-RCU.rst3 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 …]
A Dindex.rst24 NMI-RCU
/linux-6.3-rc2/Documentation/watchdog/
A Dhpwdt.rst2 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.3-rc2/Documentation/tools/rtla/
A Drtla-hwnoise.rst48 …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
A Drtla-osnoise-top.rst44 …ime Noise % CPU Aval Max Noise Max Single HW NMI IRQ S…
/linux-6.3-rc2/Documentation/core-api/
A Dentry.rst16 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.3-rc2/Documentation/trace/
A Devents-nmi.rst2 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
A Dosnoise-tracer.rst21 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.3-rc2/Documentation/devicetree/bindings/interrupt-controller/
A Drenesas,rzg2l-irqc.yaml15 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
A Dallwinner,sun6i-a31-r-intc.yaml7 title: Allwinner A31 NMI/Wakeup Interrupt Controller
41 The GIC interrupt labeled as "External NMI".
A Drenesas,rza1-irqc.yaml17 - NMI edge select.
/linux-6.3-rc2/Documentation/translations/zh_CN/admin-guide/
A Dlockup-watchdogs.rst37 Hrtimer用于周期性产生中断并唤醒watchdog线程;NMI perf事件则以”watchdog_thresh“
40 断发生,'hardlockup 检测器'(即NMI perf事件处理函数)将会视系统配置而选择产生内核
/linux-6.3-rc2/Documentation/x86/
A Dkernel-stacks.rst42 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
A Dpti.rst147 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
A Dentry_64.rst94 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)
/linux-6.3-rc2/Documentation/admin-guide/sysctl/
A Dkernel.rst600 This parameter can be used to control the NMI watchdog
611 while a CPU is busy. Hence, the alternative name 'NMI watchdog'.
750 Controls the kernel's behavior when a CPU receives an NMI caused by
755 1 Panic immediately. The IO error triggered an NMI. This indicates a
758 servers issue this sort of NMI when the dump button is pushed,
1305 be issued an NMI and instructed to capture stack trace.
1308 NMI.
1528 The value in this file affects behavior of handling NMI. When the
1532 NMI switch that most IA32 servers have fires unknown NMI up, for
1533 example. If a system hangs up, try pressing the NMI switch.
[all …]
/linux-6.3-rc2/drivers/char/mwave/
A D3780i.c408 rBootDomain.NMI = true; in dsp3780I_Reset()
443 rBootDomain.NMI = true; in dsp3780I_Run()
453 rBootDomain.NMI = false; in dsp3780I_Run()
A D3780i.h163 unsigned short NMI:1; /* RW: non maskable interrupt */ member
/linux-6.3-rc2/arch/x86/
A DKconfig.debug177 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.3-rc2/Documentation/admin-guide/
A Dlockup-watchdogs.rst42 job. An NMI perf event is generated every "watchdog_thresh"
46 'hardlockup detector' (the handler for the NMI perf event) will
/linux-6.3-rc2/Documentation/devicetree/bindings/arm/firmware/
A Dsdei.txt7 a firmware-assisted NMI.
/linux-6.3-rc2/arch/x86/kernel/
A Ddumpstack_64.c87 EPAGERANGE(NMI),
/linux-6.3-rc2/Documentation/ia64/
A Dmca.rst127 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-6.3-rc2/arch/arm/boot/dts/
A Dam335x-osd335x-common.dtsi60 interrupts = <7>; /* NMI */
/linux-6.3-rc2/Documentation/filesystems/nfs/
A Dnfs41-server.rst51 | Implementation status | Operation | REQ,REC, OPT or NMI | Feature (REQ, REC or OPT) | …
176 | Implementation status | Operation | REQ,REC, OPT or NMI | Feature (REQ, REC or OPT)…

Completed in 38 milliseconds

1234