The health spec is targeted for Real Time Alerting, in order to know when something bad had happened to a PCI device - Provide alert debug information - Self healing - If problem needs vendor support, provide a way to gather all needed debugging information.
The health contains sensors which sense for malfunction. Once sensor triggered, actions such as logs and correction can be taken. Sensors are sensing the health state and can trigger correction action. The sensors are divided into the following groups - Hardware sensor - a sensor which is triggered by the device due to malfunction. - Software sensor - a sensor which is triggered by the software due to malfunction. Both group of sensors can be triggered due to error event or due to a periodic check. Actions are the way to handle sensor events. Action can be in one of the following groups: - Dump - SW trace, SW dump, HW trace, HW dump - Reset - Surgical correction (e.g. modify Q, flush Q, reset of device, etc) Actions can be performed by SW or HW. User is allowed to enable or disable sensors and sensor2action mapping. This RFC man page patch describes the suggested API of devlink-health in order to control sensors and actions. Eran Ben Elisha (1): man: Add devlink health man page man/man8/devlink-health.8 | 171 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 171 insertions(+) create mode 100644 man/man8/devlink-health.8 -- 1.8.3.1
