Attn: Seperate handling of PHYP and Hostboot TI

When attention handler has determined that a special attention was due
to a TI it will use the TI info data to determine whether the TI was
from PHYP or hostboot and handle the individual cases as appropriate.

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