docs/designs/nmi-dbus-interface.md

7 Created: 2019-05-21
19 causing system hang(<https://github.com/ibm-openbmc/dev/issues/457>). This means
24 which, in turn, triggers an architecture-dependent procedure that fires an
30 architecture-specific procedure that enables data collection followed by
34 ### D-Bus
36 Introducing new D-Bus interface in the control.host namespace
37 (/openbmc/phosphor-dbus-interfaces/xyz/openbmc_project/Control/Host/
38 NMI.interface.yaml) and implement the new D-Bus back-end for respective
39 processor specific targets.
43 Enable NMI D-Bus phosphor interface and support this via Redfish
47 - Reference: DSP2046 2018.3,
48 - ComputerSystem 1.6.0 schema provides an action called #ComputerSystem.Reset,
52   - Nmi: Generate a Diagnostic Interrupt (usually an NMI on x86 systems) to
56 ## High-Level Flow
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
67    specific actions. One such action could be; invoking the kdump followed by
70 - Note: NMI can be sent to the host in any state, not just at an unresponsive
75 Extending the existing D-Bus interface state.Host namespace
76 (/openbmc/phosphor-dbus-interfaces/xyz/openbmc_project/State/Host.interface.yaml)
77 to support new RequestedHostTransition property called Nmi. D-Bus back-end can
78 internally invoke processor-specific target to invoke NMI and do associated
82 phosphor-state-manager has always been focused on the states of the BMC,
87 This implementation only needs to make some changes to the system state when NMI