Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-libhei / a1c5fa5a0ec21645d145198cae2f304a9465952f
commita1c5fa5a0ec21645d145198cae2f304a9465952f[log] [tgz]
authorCaleb Palmer <cnpalmer@us.ibm.com>Mon Apr 21 08:41:32 2025 -0500
committerCaleb Palmer <cnpalmer@us.ibm.com>Mon Apr 21 08:42:12 2025 -0500
treedd74b34a2db17d8c2425512124acf0ce5d98139e
parent19eeabecc411c97fad73f39d2666abee4d6679bd [diff]
Fix extra signature file path in pel parsing

Change-Id: Ia73a1e6ca066d5af9417313a34c744ab0e125f9a
Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com>
6 files changed
tree: dd74b34a2db17d8c2425512124acf0ce5d98139e
  1. chip_data/
  2. src/
  3. subprojects/
  4. test/
  5. .clang-format
  6. .eslintignore
  7. .gitignore
  8. .prettierignore
  9. .prettierrc.yaml
  10. buildinfo.hpp.in
  11. LICENSE
  12. meson.build
  13. meson.options
  14. OWNERS
  15. README.md
README.md

openpower-libhei: Hardware Error Isolation for POWER Systems

This library is a common, portable code base for isolating errors reported by hardware registers on POWER Systems chips.

The primary consumers (and requirements drivers) will be:

Core API

See the primary API definitions for details on how to use this library.

Integration

This library can be integrated into a user application's source (either imported, or as a git subtree/submodule) or built as static library.

User Application Requirements and APIs

  • The process to access hardware register data will vary per user application. Therefore, this library will declare the hardware access user APIs, but each user application must implement the APIs for their own environment.
  • This library will not contain data regarding hardware specific information. Instead, that information will be provided by the user application in the form of the Chip Data Files.
  • Tracing, or logging, methods will vary per user application. Therefore, this library will declare the tracing/logging user APIs, but each user application must implement the APIs for their own environment.

Environment configuration

  • __HEI_ENABLE_HW_WRITE: When defined, it will allow hardware write support. Note that the Chip Data Files will contain rules for clearing and masking register bits. Both of which will require modifying hardware registers, which is not allowed by user applications like OpenBMC or FSP firmware.

Development Notes

  • The Hostboot environment only supports up to C++14. Therefore, this library cannot use anything newer at this time.
  • Hostboot has a very limited environment. It does not include libc or libstdc++. However, Hostboot has implemented select functions from those libraries as needed. For details, you can reference src/include/ in the POWER Systems Hostboot firmware.

Building

For a standard OpenBMC release build, you want something like:

meson -Dtests=disabled <build_dir>
ninja -C <build_dir>
ninja -C <build_dir> install

For a test / debug build, a typical configuration is:

meson -Dtests=enabled <build_dir>
ninja -C <build_dir> test