/linux/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:: 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 …]
|
H A D | index.rst | 24 NMI-RCU
|
/linux/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/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/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/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/Documentation/translations/zh_CN/admin-guide/ |
H A D | lockup-watchdogs.rst | 37 Hrtimer用于周期性产生中断并唤醒watchdog线程;NMI perf事件则以”watchdog_thresh“ 40 断发生,'hardlockup 检测器'(即NMI perf事件处理函数)将会视系统配置而选择产生内核
|
/linux/Documentation/translations/zh_TW/admin-guide/ |
H A D | lockup-watchdogs.rst | 37 Hrtimer用於週期性產生中斷並喚醒watchdog線程;NMI perf事件則以”watchdog_thresh“ 40 斷髮生,'hardlockup 檢測器'(即NMI perf事件處理函數)將會視系統配置而選擇產生內核
|
/linux/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
|
H A 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)
|
/linux/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/Documentation/admin-guide/sysctl/ |
H A D | kernel.rst | 374 If this option is set, the kernel will send an NMI to all CPUs to dump 656 This parameter can be used to control the NMI watchdog 667 while a CPU is busy. Hence, the alternative name 'NMI watchdog'. 669 The NMI watchdog is disabled by default if the kernel is running as a guest 681 Factor to apply to the NMI watchdog timeout (only when ``nmi_watchdog`` is 683 ``watchdog_thresh`` when calculating the NMI watchdog timeout during an 686 A value of 0 means no change. The default value is 200 meaning the NMI 735 If this option is set, the kernel will send an NMI to all CPUs to dump 806 Controls the kernel's behavior when a CPU receives an NMI caused by 811 1 Panic immediately. The IO error triggered an NMI. This indicates a [all …]
|
/linux/arch/x86/kernel/ |
H A D | fred.c | 84 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/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()
|
H A D | 3780i.h | 163 unsigned short NMI:1; /* RW: non maskable interrupt */ member
|
/linux/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/Documentation/devicetree/bindings/arm/firmware/ |
H A D | sdei.txt | 7 a firmware-assisted NMI.
|
/linux/Documentation/filesystems/nfs/ |
H A D | nfs41-server.rst | 51 | 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)…
|
/linux/arch/arm/boot/dts/ti/omap/ |
H A D | am335x-osd335x-common.dtsi | 61 interrupts = <7>; /* NMI */
|
/linux/Documentation/translations/zh_CN/core-api/ |
H A D | local_ops.rst | 37 断处理程序,它允许在NMI(Non Maskable Interrupt)处理程序中使用连贯的计数器。
|