Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / cd6373d34e0f38965f3650d3da98d0744bb6ecf3
commitcd6373d34e0f38965f3650d3da98d0744bb6ecf3[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Thu May 12 16:49:56 2022 -0500
committerZane Shelley <zshelle@us.ibm.com>Mon May 16 13:56:35 2022 -0500
treee04a52d0d2ca7f81d15a231fb46fa349e93c084d
parent026e5a3fee904d9ff41fe89e8ceb134c09aebaf0 [diff]
Ignore analysis of OCMBs that have been masked

Attentions from OCMBs chip will flow through their connected processor
chips. We should not do analysis of those attentions if they are masked
on the connected processor chip regardless if the OCMB chip shows any
active attentions. This will take care of scenarios like a channel
failure attention that has already been handled and masked by the host
firmware.

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I2c170ea4770ad3a229c1c65fa50b056fc8a6e4b2
2 files changed
tree: e04a52d0d2ca7f81d15a231fb46fa349e93c084d
  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