Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / c08f5ff77436510fe9286fa48ae5f024e0986db5
commitc08f5ff77436510fe9286fa48ae5f024e0986db5[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Thu Jun 26 16:58:39 2025 -0500
committerZane Shelley <zshelle@us.ibm.com>Thu Jun 26 16:58:39 2025 -0500
tree782187e131315ce645dd63da56bda229d9db2bd0
parent0cab8ada29d783a1008285ca2166b5af632eaa26 [diff]
fix resolution issue with duplicate callouts

If two resolutions end up calling out the same part or procedure, only
the callout with the high priority should be added to the callout list.
This worked for the most. However, it did not take into account that the
guard action may have changed between callouts.

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