Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / 2f26318121b41f304b5ab6b738eb89087426b016
commit2f26318121b41f304b5ab6b738eb89087426b016[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Fri Jul 10 21:41:21 2020 -0500
committerZane Shelley <zshelle@us.ibm.com>Tue Aug 11 20:32:10 2020 +0000
tree54a74ddf6fbbe435a85fa02a3c5bbb1978c9ede2
parent89c0a7af33236c1963be6fe5673d7134fbb71555 [diff]
added analyzer traces for debug

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I2ff65de0cbf6893359c5dbc5096c7382749fb4da
2 files changed
tree: 54a74ddf6fbbe435a85fa02a3c5bbb1978c9ede2
  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