Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / ca49619871ab7f914dbd4b939fe81851cb927dc9
commitca49619871ab7f914dbd4b939fe81851cb927dc9[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Mon Aug 09 12:05:52 2021 -0500
committerZane Shelley <zshelle@us.ibm.com>Tue Aug 10 16:29:46 2021 -0500
treef3d97645b7b749a8e1d5f5ae79563ebc8d6d88df
parent723fa239abb755460bac08cc37209a618c1e5cf1 [diff]
ServiceData class query for system checkstop

When managing resolutions, we'll need to know if a system checkstop has
occurred. This information can be retrieved from the isolation data, but
that object is not available to the resolutions. So storing it in the
service data as well.

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