Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / a00426f5e88b9d56a7e578971c3c0b7c21a58e1c
commita00426f5e88b9d56a7e578971c3c0b7c21a58e1c[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Thu Nov 04 10:50:50 2021 -0500
committerZane Shelley <zshelle@us.ibm.com>Thu Nov 04 11:02:08 2021 -0500
tree8900db01bd76ea747c8938d75bd9d380c7090aca
parent9a738f7ff5d706e931cc6aefa6436e43cf10f32b [diff]
Removed old guard design

RAS decision is to initiate guard through the callout section in the
PELs instead of issuing a dbus message after the PEL has been committed.
So removing the old design.

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