| commit | 08698b13c01a7dce3783fe332fab1ec441b0dfac | [log] [tgz] |
|---|---|---|
| author | Johnathan Mantey <johnathanx.mantey@intel.com> | Thu Nov 07 13:06:20 2024 -0800 |
| committer | Johnathan Mantey <johnathanx.mantey@intel.com> | Thu Nov 07 13:54:33 2024 -0800 |
| tree | de78bc4ef02b3e1f6fec0ddf9bd13b4e81a9d15d | |
| parent | 1e91299e309214c5d2b00948eb4cd075a7930c91 [diff] |
Reliably report the BMC Ready state A very rare corner case was found when reporting BMC Ready. The D-Bus matching function needed to be initialized prior to reading the associated D-Bus property and saving it to a global variable. There was a small slice of time where the D-Bus entry could be updated, and the associated update event dropped. A test script was created to increase the likelihood of landing in the critical point where the BMC Ready event is dropped. Tested: Ran the test script and it failed in under 30 runs. Ran the same script on this change, which ran for 370+ passes. Change-Id: Ic4fca745452eee392e8ff5a3f1b5f39200dfc21d Signed-off-by: Johnathan Mantey <johnathanx.mantey@intel.com>
This component is intended to provide Intel-specific IPMI[3] command handlers for OpenBMC. These handlers are intended to integrate BMC with servers based on Intel architecture.
intel-ipmi-oem serves as an extension[1] to OpenBMC IPMI daemon[2]. It is compiled as a shared library and intended to both:
Related features provided by the library are grouped in separate source files. Main extensions to vanilla OpenBMC IPMI stack are the following:
[4]