Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / e4f5dbef747fb2a95768ba4fcf6286f559056bd7
commite4f5dbef747fb2a95768ba4fcf6286f559056bd7[log] [tgz]
authorBen Tyner <ben.tyner@ibm.com>Mon Oct 19 07:19:33 2020 -0500
committerBen Tyner <ben.tyner@ibm.com>Mon Oct 19 07:19:33 2020 -0500
treecccaca90138a164cd54b0ea7923949e89a7bd9ad
parent04cbbb3d3a86a2fa948f73ad60f596fd5c751ffb [diff]
Attn: Default special attention changed to TI

When a special attention occurs the attention handler uses the get TI
info chipop to determine whether to service either a TI or a
breakipoint. If this chipop is not available or is not functional the
attention handler will assume a TI has occurred. With this new behavior
an additional attention handler configuration option was added
(--defaultbreakpoint) which will allow breakpoints to be handled on
systems where the get TI info chipop is not available or not functional.

Signed-off-by: Ben Tyner <ben.tyner@ibm.com>
Change-Id: I1b386b5daf06021acd6567fdad39c21903e2ac3b
6 files changed
tree: cccaca90138a164cd54b0ea7923949e89a7bd9ad
  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