Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-libhei / fc7ab19615f5d4951fad5e7302cff2f5461290b7
commitfc7ab19615f5d4951fad5e7302cff2f5461290b7[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Fri Sep 27 15:45:16 2019 -0500
committerZane Shelley <zshelle@us.ibm.com>Thu Oct 03 21:51:04 2019 -0500
treef8b674266e75babefb76f787ad978ddd3a660395
parent200c345e8a43b6af5192922288bc27b7d727da1b [diff]
Replaced ported prdfScanFacility.[HC]

The ScanFacility was just a bunch of wrapper functions for the
flyweights. I eliminated the wrappers by making singletons for each
flyweight.

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I8ff96f33da2d52e2c1abc3556d094dabcf441945
5 files changed
tree: f8b674266e75babefb76f787ad978ddd3a660395
  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 in the common includes header.
  • 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 common includes header.

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.