Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / 7ae9c8c792489587ef44fe945646ec3837492d0a
commit7ae9c8c792489587ef44fe945646ec3837492d0a[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Wed Dec 02 20:10:31 2020 -0600
committerZane Shelley <zshelle@us.ibm.com>Wed Dec 02 20:10:31 2020 -0600
treea991b8105bc8edc23f07e67e2b1fba57cf6b0781
parentd9573f489eae420fc73709ed62eabb68dad444ff [diff]
Avoid analyzing hardware on legacy processors

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