Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / f685afd631a2fe71b6f29ca0ab49b65327399404
commitf685afd631a2fe71b6f29ca0ab49b65327399404[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Mon Feb 15 15:39:44 2021 -0600
committerZane Shelley <zshelle@us.ibm.com>Thu Feb 18 17:20:44 2021 +0000
treec0d6557870898368155438a322b475725168c68a
parentb3eba2992926f9fc55a836d2baab85adfdf9bc5d [diff]
created Callout classes for various PEL callouts

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: Ia36c52281ebd425ab1c38be57ff35ea19ee01740
3 files changed
tree: c0d6557870898368155438a322b475725168c68a
  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