| /openbmc/openpower-proc-control/ |
| H A D | nmi_interface.hpp | 12 using Base = sdbusplus::xyz::openbmc_project::Control::Host::server::NMI;
18 class NMI : public Interface class
21 NMI() = delete;
22 NMI(const NMI&) = delete;
23 NMI& operator=(const NMI&) = delete;
24 NMI(NMI&&) = delete;
25 NMI& operator=(NMI&&) = delete;
26 virtual ~NMI() = default;
32 NMI(sdbusplus::bus_t& bus, const char* path);
|
| H A D | nmi_interface.cpp | 34 NMI::NMI(sdbusplus::bus_t& bus, const char* path) : in NMI() function in openpower::proc::NMI
38 void NMI::nmi() in nmi()
|
| H A D | nmi_main.cpp | 33 openpower::proc::NMI NMI(bus, BUSPATH_NMI); in main() local
|
| /openbmc/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
|
| /openbmc/docs/designs/ |
| H A D | nmi-dbus-interface.md | 1 # Design proposal for issuing NMI on servers that use OpenBMC
23 Whenever the host is unresponsive/running, Admin needs to trigger an NMI event
29 This proposal aims to trigger NMI, which in turn will invoke an
38 NMI.interface.yaml) and implement the new D-Bus back-end for respective
43 Enable NMI D-Bus phosphor interface and support this via Redfish
51 An NMI type
52 - Nmi: Generate a Diagnostic Interrupt (usually an NMI on x86 systems) to
62 {"Action":"ComputerSystem.Reset","ResetType":"Nmi"} to trigger NMI.
63 3. Redfish URI will invoke a D-Bus NMI back-end call which will use an arch
64 specific back-end implementation of xyz.openbmc_project.Control.Host.NMI to
[all …]
|
| /openbmc/openbmc-test-automation/openpower/ |
| H A D | test_nmi_interface.robot | 18 Trigger NMI When OPAL/Host OS Is Not Up
20 ... while injecting NMI when HOST OS is not up.
24 Trigger NMI
27 Trigger NMI When OPAL/Host OS Is Running And Secureboot Is Disabled
29 ... while injecting NMI, when HOST OS is running and
34 Trigger NMI valid_status_codes=[${HTTP_OK}]
35 Verify Crash Dump Directory After NMI Inject
40 Verify Crash Dump Directory After NMI Inject
41 [Documentation] Verification of crash dump directory after NMI inject.
69 Trigger NMI
[all …]
|
| /openbmc/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
|
| /openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/Chassis/Buttons/NMI/ |
| H A D | meson.build | 3 sdbusplus_current_path = 'xyz/openbmc_project/Chassis/Buttons/NMI'
8 '../../../../../../yaml/xyz/openbmc_project/Chassis/Buttons/NMI.interface.yaml',
28 'xyz/openbmc_project/Chassis/Buttons/NMI',
|
| /openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/Control/Host/NMI/ |
| H A D | meson.build | 3 sdbusplus_current_path = 'xyz/openbmc_project/Control/Host/NMI'
8 '../../../../../../yaml/xyz/openbmc_project/Control/Host/NMI.interface.yaml',
28 'xyz/openbmc_project/Control/Host/NMI',
|
| /openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/Control/Host/ |
| H A D | meson.build | 2 subdir('NMI') subdir
51 '../../../../../yaml/xyz/openbmc_project/Control/Host/NMI.interface.yaml',
53 output: ['NMI.md'],
65 'xyz/openbmc_project/Control/Host/NMI',
|
| /openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/Chassis/Buttons/ |
| H A D | meson.build | 5 subdir('NMI') subdir
86 '../../../../../yaml/xyz/openbmc_project/Chassis/Buttons/NMI.interface.yaml',
88 output: ['NMI.md'],
100 'xyz/openbmc_project/Chassis/Buttons/NMI',
|
| /openbmc/qemu/include/hw/ |
| H A D | nmi.h | 30 DECLARE_CLASS_CHECKERS(NMIClass, NMI,
32 #define NMI(obj) \ macro
|
| /openbmc/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
|
| /openbmc/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
|
| /openbmc/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.
|
| /openbmc/openpower-proc-control/service_files/ |
| H A D | xyz.openbmc_project.Control.Host.NMI.service.in | 2 Description=Start the Open Power Host Control NMI service
13 BusName=xyz.openbmc_project.Control.Host.NMI
|
| /openbmc/openbmc/meta-asrock/meta-e3c256d4i/recipes-x86/chassis/x86-power-control/ |
| H A D | power-config-host0.json | 19 // NMI on the host), but as a workaround treating the NMI_BTN_N line
20 // (normally the NMI button input) instead as an output and driving
|
| /openbmc/linux/Documentation/translations/zh_CN/admin-guide/ |
| H A D | lockup-watchdogs.rst | 37 Hrtimer用于周期性产生中断并唤醒watchdog线程；NMI perf事件则以”watchdog_thresh“
40 断发生，'hardlockup 检测器'(即NMI perf事件处理函数)将会视系统配置而选择产生内核
|
| /openbmc/openbmc/meta-yadro/meta-nicole/recipes-phosphor/host/op-proc-control/ |
| H A D | 0001-Stop-and-send-SRESET-for-one-thread-only.patch | 27 @@ -38,7 +38,7 @@ void NMI::nMI()
36 @@ -51,11 +51,19 @@ void NMI::nMI()
|
| /openbmc/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 | 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
|
| /openbmc/linux/Documentation/admin-guide/sysctl/ |
| H A D | kernel.rst | 356 If this option is set, the kernel will send an NMI to all CPUs to dump
629 This parameter can be used to control the NMI watchdog
640 while a CPU is busy. Hence, the alternative name 'NMI watchdog'.
642 The NMI watchdog is disabled by default if the kernel is running as a guest
654 Factor to apply to the NMI watchdog timeout (only when ``nmi_watchdog`` is
656 ``watchdog_thresh`` when calculating the NMI watchdog timeout during an
659 A value of 0 means no change. The default value is 200 meaning the NMI
708 If this option is set, the kernel will send an NMI to all CPUs to dump
779 Controls the kernel's behavior when a CPU receives an NMI caused by
784 1 Panic immediately. The IO error triggered an NMI. This indicates a
[all …]
|