Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-libhei / 5a26661c1f8f9b8c9910f64f6265485f4e6f441f
commit5a26661c1f8f9b8c9910f64f6265485f4e6f441f[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Thu Aug 15 16:23:53 2019 -0500
committerZane Shelley <zshelle@us.ibm.com>Thu Aug 15 16:26:51 2019 -0500
treeb68e6bc43add30efc3b7a6da51472b6873f64469
parentf85bb66c85bf5d671b6693296a9f68a40d94d218 [diff]
Created primary API wrappers for the Isolator class

This is an attempt to abstract the internal workings of the isolator
class from the user application.

Change-Id: Ic898b202da6a0ddb368411c11218ca019d1f23fd
Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
10 files changed
tree: b68e6bc43add30efc3b7a6da51472b6873f64469
  1. src/
  2. test/
  3. .gitignore
  4. LICENSE
  5. MAINTAINERS
  6. meson.build
  7. meson_options.txt
  8. 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 is intended to be integrated into containing user applications as a set of source files (either imported, or as a git subtree/submodule).

Details TBD.

User Application Requirements and APIs

  • The method to access hardware register data will vary per user application. Therefore, this library will declare the hardware access user APIs, but each containing 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. Specifically, FSP and Hostboot firmware utilize specialized macros as a mechanism to save code image space. Therefore, the user application will need to provide a specific header file that defines these macros. Details are included in the user APIs.
  • Methods to assert programming bugs will vary per user application. Therefore, much like tracing, the user application will need to provide a specific header file that defines macros for assertion. Details are included in the user APIs.

Environment configuration

  • __HEI_READ_ONLY: When defined, it will ensure any hardware write support is disabled. 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 and FSP environments only support up to C++11. 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.