Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-libhei / cef6349ad57fd1db16f3206262a0a77734e5548c
commitcef6349ad57fd1db16f3206262a0a77734e5548c[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Mon Jan 11 16:52:40 2021 -0600
committerZane Shelley <zshelle@us.ibm.com>Tue Jan 12 02:31:30 2021 +0000
treee3cebcfa3bf143fd27bacdee99d139365925387a
parentf8a726b7cf54ad457aff25389db1c43fc277c13d [diff]
Proper handling for unused parameter

Instead of ignoring the parameter warning via a compile flag we can
explicitly not give the parameter a valiable name. The compile will then
know that that the parameter is not expected to be used.

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I140f07eaad737f44c4791f37249f89849da15cae
2 files changed
tree: e3cebcfa3bf143fd27bacdee99d139365925387a
  1. src/
  2. test/
  3. xml/
  4. .clang-format
  5. .gitignore
  6. LICENSE
  7. MAINTAINERS
  8. meson.build
  9. meson_options.txt
  10. 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