| /linux-4.1.27/Documentation/watchdog/ |
| D | hpwdt.txt | 3 HP iLO2 NMI Watchdog Driver
4 NMI sourcing for iLO2 based ProLiant Servers
8 The HP iLO2 NMI Watchdog driver is a kernel module that provides basic
9 watchdog functionality and the added benefit of NMI sourcing. Both the
10 watchdog functionality and the NMI sourcing capability need to be enabled
12 A user can have the NMI sourcing without the watchdog timer and vice-versa.
25 allow_kdump - allows the user to save off a kernel dump image after an NMI
31 enable NMI sourcing then reload the hpwdt driver with
42 The NMI sourcing capability is disabled by default due to the inability to
43 distinguish between "NMI Watchdog Ticks" and "HW generated NMI events" in the
[all …]
|
| D | watchdog-api.txt | 110 actual time they will reset the system. This can be done with an NMI,
|
| D | watchdog-parameters.txt | 180 0 = RESET(*) 1 = SMI 2 = NMI 3 = SCI
|
| /linux-4.1.27/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 …]
|
| D | 00-INDEX | 13 NMI-RCU.txt
14 - Using RCU to Protect Dynamic NMI Handlers
|
| D | whatisRCU.txt | 336 NMI enter / NMI exit
346 c. RCU applied to scheduler and interrupt/NMI-handler tasks.
356 uses of RCU may be found in listRCU.txt, arrayRCU.txt, and NMI-RCU.txt.
439 arrayRCU.txt, and NMI-RCU.txt.
904 c. Do you need to treat NMI handlers, hardirq handlers,
|
| D | checklist.txt | 20 is the dynamic NMI code in the Linux 2.6 kernel, at least on
326 If you want to wait for interrupt handlers, NMI handlers, and
|
| D | trace.txt | 115 is the NMI nesting depth.
|
| D | RTFP.txt | 2144 and NMI processing for hierarchical RCU's dynticks interface.
|
| /linux-4.1.27/Documentation/devicetree/bindings/interrupt-controller/ |
| D | allwinner,sun67i-sc-nmi.txt | 1 Allwinner Sunxi NMI Controller
14 - interrupts: Specifies the interrupt line (NMI) which is handled by
16 shall be the NMI.
|
| /linux-4.1.27/arch/mn10300/kernel/ |
| D | entry.S | 276 # NMI exception entry points
279 # in addition to the main NMI and Watchdog channels. SMP NMI IPIs use this
299 mov GxICR_DETECT,d0 # clear NMI request
302 and ~EPSW_NMID,epsw # enable NMI
312 bne nmi_not_debugger # if not kernel debugger NMI IPI, jump
314 # kernel debugger NMI IPI
316 mov GxICR_DETECT,d0 # clear NMI
319 and ~EPSW_NMID,epsw # enable NMI
351 and ~EPSW_NMID,epsw # turn NMIs back on if not NMI
|
| /linux-4.1.27/Documentation/trace/ |
| D | events-nmi.txt | 1 NMI Trace Events
12 NMI handlers are hogging large amounts of CPU time. The kernel
15 INFO: NMI handler took too long to run: 9.207 msecs
|
| D | ftrace-design.txt | 210 If you can't trace NMI functions, then skip this option.
|
| /linux-4.1.27/Documentation/x86/x86_64/ |
| D | kernel-stacks | 33 double fault or NMI, which makes it easier to handle these unusual
51 NMI. arch/x86_64/kernel/entry.S::paranoidentry adjusts the stack
77 Used for non-maskable interrupts (NMI).
79 NMI can be delivered at any time, including when the kernel is in the
80 middle of switching stacks. Using IST for NMI events avoids making
|
| /linux-4.1.27/arch/cris/ |
| D | Kconfig.debug | 28 bool "NMI causes oops printout"
32 here to make it possible to dump an OOPS with an external NMI.
|
| /linux-4.1.27/arch/c6x/kernel/ |
| D | vectors.S | 66 IRQVEC NMI,_nmi_handler ; NMI interrupt
|
| /linux-4.1.27/Documentation/sysctl/ |
| D | kernel.txt | 422 This parameter can be used to control the NMI watchdog
431 while a CPU is busy. Hence, the alternative name 'NMI watchdog'.
433 The NMI watchdog is disabled by default if the kernel is running as a guest
567 The default Linux behaviour on an NMI of either memory or unknown is
572 A small number of systems do generate NMI's for bizarre random reasons
817 be issued an NMI and instructed to capture stack trace.
820 NMI.
839 the watchdog timer function, otherwise the NMI watchdog - if enabled - can
898 The value in this file affects behavior of handling NMI. When the
899 value is non-zero, unknown NMI is trapped and then panic occurs. At
[all …]
|
| /linux-4.1.27/Documentation/frv/ |
| D | gdbstub.txt | 9 permits the NMI interrupt button or serial port events to jump the kernel into
14 generate level 15 interrupts (NMI). The kernel proper cannot see the serial
118 (*) Pressing the NMI button on the board will also cause a jump into the
|
| /linux-4.1.27/Documentation/ |
| D | lockup-watchdogs.txt | 40 task. An NMI perf event is generated every "watchdog_thresh"
44 'hardlockup detector' (the handler for the NMI perf event) will
|
| D | IPMI.txt | 608 interrupts, and "pre_nmi" for a NMI on a preaction. This is how
615 because you can't do data operations from an NMI.
644 Note that if you use the NMI preaction for the watchdog, you MUST NOT
645 use the nmi watchdog. There is no reasonable way to tell if an NMI
647 otherwise unhandled NMI, it must be from IPMI and it will panic
|
| D | local_ops.txt | 27 coherent counters in NMI handlers. It is especially useful for tracing purposes
|
| D | edac.txt | 95 NMI NMI notification of ECC errors
|
| D | kernel-parameters.txt | 2273 when a NMI is triggered.
2281 When panic is specified, panic when an NMI watchdog
2459 nonmi_ipi [X86] Disable using NMI IPIs during panic/reboot to
2504 soft-lockup and NMI watchdog (hard-lockup).
2570 timer: [X86] Force use of architectural NMI
3740 [X86] Cause panic on unknown NMI.
|
| D | memory-barriers.txt | 1519 a nested interrupt or an NMI. Otherwise, ACCESS_ONCE() is not
|
| D | devices.txt | 2899 8 = /dev/cpqhealth/cnmi NMI Handling
|
| /linux-4.1.27/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-4.1.27/arch/x86/ |
| D | Kconfig.debug | 301 bool "NMI Selftest"
304 Enabling this option turns on a quick NMI selftest to verify
305 that the NMI behaves correctly.
307 This might help diagnose strange hangs that rely on NMI to
|
| D | Kconfig | 899 performance counters), and the NMI watchdog which detects hard
|
| /linux-4.1.27/Documentation/x86/ |
| D | entry_64.txt | 88 But if we are in an NMI/MCE/DEBUG/whatever super-atomic entry context,
93 Therefore, super-atomic entries (except NMI, which is handled separately)
|
| D | boot.txt | 1016 entering protected mode. The default routine disables NMI, so
|
| /linux-4.1.27/Documentation/ia64/ |
| D | mca.txt | 123 How is ia64 MCA/INIT different from x86 NMI?
125 * x86 NMI typically gets delivered to one cpu. MCA/INIT gets sent to
128 * x86 NMI cannot be nested. MCA/INIT can be nested, to a depth of 2
135 * x86 does not call the BIOS so the NMI handler does not have to worry
|
| /linux-4.1.27/arch/avr32/ |
| D | Kconfig | 223 bool "NMI Debugging"
227 the kernel to turn on NMI debugging. Depending on the value
|
| /linux-4.1.27/drivers/acpi/apei/ |
| D | Kconfig | 15 to the operating system. This improves NMI handling
|
| /linux-4.1.27/arch/blackfin/ |
| D | Kconfig.debug | 56 handler, the NMI handler, the reset vector, or in emulator mode,
212 bool "Enable NMI watchdog to help debugging lockup on SMP"
217 interrupt for more than 5 seconds, then the NMI handler dumps debug
|
| D | Kconfig | 701 - RETN: Non-Maskable Interrupt (NMI)
712 safely use NMI on the Blackfin while running Linux, but
725 and the NMI.
736 ICE and use the NMI.
|
| /linux-4.1.27/arch/cris/arch-v10/kernel/ |
| D | entry.S | 417 ;; special handlers for breakpoint and NMI
445 ;; If there is a glitch on the NMI pin shorter than ~100ns
451 move.d [R_IRQ_MASK0_RD], $r1 ; External NMI or watchdog?
456 setf m ; Enable NMI again
|
| /linux-4.1.27/Documentation/devicetree/bindings/mfd/ |
| D | axp20x.txt | 11 - interrupts: SoC NMI / GPIO interrupt connected to the PMIC's IRQ pin
|
| /linux-4.1.27/Documentation/arm64/ |
| D | acpi_object_usage.txt | 531 APEI requires the equivalent of an SCI and an NMI on ARMv8. The SCI is used
533 system can continue correct operation, even if possibly degraded. The NMI is
537 Since there is no direct equivalent of the x86 SCI or NMI, arm64 handles
540 reported, this is sufficient. The NMI is emulated as the highest priority
543 at the same priority as the emulated NMI. In Linux, this should not be the
|
| /linux-4.1.27/Documentation/devicetree/bindings/c6x/ |
| D | interrupt.txt | 7 C64X+ core. Priority 0 and 1 are used for reset and NMI respectively.
|
| /linux-4.1.27/include/trace/events/ |
| D | kvm.h | 16 ERSN(NMI), ERSN(INTERNAL_ERROR), ERSN(OSI), ERSN(PAPR_HCALL), \
|
| /linux-4.1.27/arch/blackfin/mach-bf518/ |
| D | Kconfig | 141 bool "Enable Hysteresis on {NMI, RESET, BMODE}"
|
| /linux-4.1.27/Documentation/x86/i386/ |
| D | IO-APIC.txt | 28 NMI: 0
|
| /linux-4.1.27/arch/blackfin/mach-bf527/ |
| D | Kconfig | 143 bool "Enable Hysteresis on {NMI, RESET, BMODE}"
|
| /linux-4.1.27/arch/x86/kernel/ |
| D | head_64.S | 357 je is_nmi # Ignore NMI
|
| D | head_32.S | 560 je is_nmi # Ignore NMI
|
| /linux-4.1.27/arch/frv/kernel/ |
| D | entry-table.S | 129 # handler declaration for an NMI external interrupt
|
| D | entry.S | 169 # raise the minimum interrupt priority to 15 (NMI only) and enable exceptions
|
| /linux-4.1.27/arch/sh/kernel/cpu/sh3/ |
| D | entry.S | 486 * expected path for the NMI (and any other brilliantly implemented
|
| /linux-4.1.27/drivers/pinctrl/ |
| D | pinctrl-xway.c | 119 MFP_XWAY(GPIO8, GPIO, CGU, NMI, NONE),
310 GRP_MUX("nmi", NMI, pins_nmi),
|
| /linux-4.1.27/drivers/watchdog/ |
| D | Kconfig | 818 A software monitoring watchdog and NMI sourcing driver. This driver
836 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
840 When an NMI occurs this feature will make the necessary BIOS calls to
841 log the cause of the NMI.
1197 installs a NMI handler and pokes the watchdog based on an
1200 NMI that prints a message. The third expiration causes a
|
| /linux-4.1.27/arch/blackfin/mach-bf518/include/mach/ |
| D | defBF512.h | 1296 #define NMI 0x4 /* Non Maskable Interrupt */ macro
|
| /linux-4.1.27/arch/score/kernel/ |
| D | entry.S | 115 ENTRY(handle_nmi) # NMI #1
|
| /linux-4.1.27/arch/blackfin/mach-bf527/include/mach/ |
| D | defBF522.h | 1301 #define NMI 0x4 /* Non Maskable Interrupt */ macro
|
| /linux-4.1.27/Documentation/timers/ |
| D | timekeeping.txt | 143 NMI-safe and return a sane value in any context.
|
| /linux-4.1.27/drivers/tty/serial/ |
| D | Kconfig | 168 bool "Serial console over KGDB NMI debugger port"
171 This special driver allows you to temporary use NMI debugger port
176 This is because this console driver processes the input in NMI
181 detach debugger port from the KGDB NMI (i.e. disable_nmi), and
|
| /linux-4.1.27/Documentation/locking/ |
| D | lockdep-design.txt | 201 We also assume that all NMI/SMM paths [which could interrupt
|
| /linux-4.1.27/arch/blackfin/mach-bf548/include/mach/ |
| D | defBF54x_base.h | 1985 #define NMI 0x4 /* Non Maskable Interrupt */ macro
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | proc.txt | 617 NMI: 0
637 NMI: 2457961 2457959
641 NMI is incremented in this case because every timer interrupt generates a NMI
642 (Non Maskable Interrupt) which is used by the NMI Watchdog to detect lockups.
|
| /linux-4.1.27/arch/ |
| D | Kconfig | 262 System hardware can generate an NMI using the perf event
|
| /linux-4.1.27/Documentation/kdump/ |
| D | kdump.txt | 428 If a hard lockup is detected and "NMI watchdog" is configured, the system
|
| /linux-4.1.27/arch/sparc/kernel/ |
| D | entry.S | 324 be sun4m_nmi_error ! Must be an NMI async memory error
|
| /linux-4.1.27/lib/ |
| D | Kconfig.debug | 699 An NMI is generated every 10 seconds or so to check for hardlockups.
701 The frequency of hrtimer and NMI events and the soft and hard lockup
927 best used in conjunction with the NMI watchdog so that spinlock
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | api.txt | 1743 Queues an NMI on the thread's vcpu. Note this is well defined only
1753 - check whether changing LINT1 will queue an NMI (see the LVT entry for LINT1)
1757 Some guests configure the LINT1 NMI input to cause a panic, aiding in
|