Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / fe15649ef9bcc45513cec53cbd3f403ab2ddee8a
commitfe15649ef9bcc45513cec53cbd3f403ab2ddee8a[log] [tgz]
authorBen Tyner <ben.tyner@ibm.com>Thu Apr 08 07:28:13 2021 -0500
committerZane Shelley <zshelle@us.ibm.com>Fri Apr 09 18:16:49 2021 +0000
treeb2e08624e2d331ddd86b93a0b7b6770549fb41d9
parentfeeea83b3fc9aabd23a1ec6d29bd293008954acc [diff]
Attn: Remove --defaultbreakpoint add --defaultti

In order to support breakpoint handling and TI handling on systems that
did not support the get TI info interface the --defaultbreakpoint
configuration option was added. This switch is no longer needed and
breakpoint handling is now the default action for available but invalid
TI info data. A new option --defaultti was added to force handling of
TI's when TI info is available but not valid.

Signed-off-by: Ben Tyner <ben.tyner@ibm.com>
Change-Id: I4bdf90dcbbf20b3428a1cef6f1a71ec32b3ca238
6 files changed
tree: b2e08624e2d331ddd86b93a0b7b6770549fb41d9
  1. analyzer/
  2. attn/
  3. subprojects/
  4. test/
  5. util/
  6. .clang-format
  7. .gitignore
  8. cli.cpp
  9. cli.hpp
  10. config.h.in
  11. LICENSE
  12. listener.cpp
  13. listener.hpp
  14. main.cpp
  15. main_nl.cpp
  16. MAINTAINERS
  17. meson.build
  18. meson_options.txt
  19. 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