Move root cause signature into service data object

This allows the analysis code to access the signature from the service
data object instead of passing around two variables in all of those
functions.

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: Ib85386759068aee26dc1e8b9e8d609daf7e63c1b
5 files changed
tree: 26e9a620efd73ac55b9b8a8bfcb5cba130e40ec4
  1. analyzer/
  2. attn/
  3. subprojects/
  4. test/
  5. util/
  6. .clang-format
  7. .gitignore
  8. cli.cpp
  9. cli.hpp
  10. LICENSE
  11. listener.cpp
  12. listener.hpp
  13. main.cpp
  14. main_nl.cpp
  15. MAINTAINERS
  16. meson.build
  17. meson_options.txt
  18. README.md
README.md

Hardware Diagnostics for POWER Systems

In the event of a system fatal error reported by the internal system hardware (processor chips, memory chips, I/O chips, system memory, etc.), POWER Systems have the ability to diagnose the root cause of the failure and perform any service action needed to avoid repeated system failures.

Aditional details TBD.

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