NVMe: Implement dynamic Log Pages (00h) detection
For the devices having nvme basic version greater than or equal to 2.0
supports 00h log which defines whether a log page is supported for that
device.
For Metric store, nvmesensor will check the basic version of the device
and if-
* version < 2.0, will keep the existing behavior and show all the
metrics that the daemon so far supported
* version >= 2.0
* will fetch 00h log page and add metric based on the relavanat
support as per 00h logapage
* if 00h log fetch fails, then no metric except Identify metric will
be added
Tested:
For a device having nvme version 0x20100, found all the metrics are showing in the list-
```
root@pnhuna-mm17-nfd01:~# curl -s localhost/redfish/v1/Systems/system/Storage/E1S_SSD_1_NVMe/Controllers/129 | jq .Oem.Google
{
"ControllerType": "NVMePF",
"DeviceSelfTestMetric": {
"DataUri": "/redfish/v1/Systems/system/Storage/E1S_SSD_1_NVMe/Controllers/129/Oem/Google/Metrics/DeviceSelfTestMetric"
},
"ErrorInfoMetric": {
"DataUri": "/redfish/v1/Systems/system/Storage/E1S_SSD_1_NVMe/Controllers/129/Oem/Google/Metrics/ErrorInfoMetric"
},
"FwSlotInfoMetric": {
"DataUri": "/redfish/v1/Systems/system/Storage/E1S_SSD_1_NVMe/Controllers/129/Oem/Google/Metrics/FwSlotInfoMetric"
},
"HostInitiatedMetric": {
"DataUri": "/redfish/v1/Systems/system/Storage/E1S_SSD_1_NVMe/Controllers/129/Oem/Google/Metrics/HostInitiatedMetric"
},
"IdentifyMetric": {
"DataUri": "/redfish/v1/Systems/system/Storage/E1S_SSD_1_NVMe/Controllers/129/Oem/Google/Metrics/IdentifyMetric"
},
"SMARTMetric": {
"DataUri": "/redfish/v1/Systems/system/Storage/E1S_SSD_1_NVMe/Controllers/129/Oem/Google/Metrics/SMARTMetric"
}
}
```
Google-Bug-Id: 404877612
Change-Id: Iae609b706cecfcbb6aa077b0497815f0552b2d08
Signed-off-by: Munawar Hussain <munawarhussain@google.com>
dbus-sensors is a collection of sensor applications that provide the xyz.openbmc_project.Sensor collection of interfaces. They read sensor values from hwmon, d-bus, or direct driver access to provide readings. Some advance non-sensor features such as fan presence, pwm control, and automatic cpu detection (x86) are also supported.
runtime re-configurable from d-bus (entity-manager or the like)
isolated: each sensor type is isolated into its own daemon, so a bug in one sensor is unlikely to affect another, and single sensor modifications are possible
async single-threaded: uses sdbusplus/asio bindings
multiple data inputs: hwmon, d-bus, direct driver access
A typical dbus-sensors object support the following dbus interfaces:
Path /xyz/openbmc_project/sensors/<type>/<sensor_name>
Interfaces xyz.openbmc_project.Sensor.Value
xyz.openbmc_project.Sensor.Threshold.Critical
xyz.openbmc_project.Sensor.Threshold.Warning
xyz.openbmc_project.State.Decorator.Availability
xyz.openbmc_project.State.Decorator.OperationalStatus
xyz.openbmc_project.Association.Definitions
Sensor interfaces collection are described here.
Consumer examples of these interfaces are Redfish, Phosphor-Pid-Control, IPMI SDR.
dbus-sensor daemons are reactors that dynamically create and update sensors configuration when system configuration gets updated.
Using asio timers and async calls, dbus-sensor daemons read sensor values and check thresholds periodically. PropertiesChanged signals will be broadcasted for other services to consume when value or threshold status change. OperationStatus is set to false if the sensor is determined to be faulty.
A simple sensor example can be found here.
Sensor devices are described using Exposes records in configuration file. Name and Type fields are required. Different sensor types have different fields. Refer to entity manager schema for complete list.