Refined guard type in HardwareCalloutResolution

A resolution guard type needs to be evaluated during the resolve()
function and not when the resolution is created.

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: Ia597ed93567b27c2cd9423f6fb0f7e75158fc315
3 files changed
tree: 064ab72f74d15aa48d63095b5e76efc3b1885877
  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