| commit | a0c6b5b75aaf67e060d8f01787434954355c84e5 | [log] [tgz] |
|---|---|---|
| author | Zhikui Ren <zhikui.ren@intel.com> | Tue Jun 06 12:14:19 2023 -0700 |
| committer | Zhikui Ren <zhikui.ren@intel.com> | Fri Aug 04 00:22:55 2023 +0000 |
| tree | 9ccf304a099c2121e47a59c717f1cda47301556b | |
| parent | cb359da1621ae8f78d41880236433729d81ea2b2 [diff] |
Add uring_args for all build targets in package io_uring backend is enabled with uring_args. Add them to package args. All build targets including static libraries for utils and thresholds and sensor services executables are built consistently. Currently steady timer in utils.cpp fires right away for services build with io_uring enabled like fansensor, hwmontempsensor. https://github.com/openbmc/dbus-sensors/blob/master/src/Utils.cpp#L472 Tested: Added debug print and verified the above timer handler is called 10 seconds after the timer is started as expected. intelcpusensor, which does not use random_access_file with io_uring backend reads sensor values successfully. Services use random_access_file read sensor data successfully. Signed-off-by: Zhikui Ren <zhikui.ren@intel.com> Change-Id: I8cf3a9a0d1ffca459eb6c2c37e4e2220ce5100ac
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.