commit | e81eb15d93922a1ce9dd1362fe06af6e2523f416 | [log] [tgz] |
---|---|---|
author | austinfcui <austinfcui@gmail.com> | Tue Apr 19 10:56:32 2022 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Apr 28 16:25:59 2022 +0000 |
tree | 6c3a630d64f83c47698d25130912ec16f51c94c4 | |
parent | 7bf1bfa508ab6434b315eb0da14fbf3cf12a86cb [diff] |
Add a UT function for getActiveChips() of util/pdbg files Signed-off-by: austinfcui <austinfcui@gmail.com> Change-Id: I22fed946eaa7f4c11c52df9e2c5aa3ab734b033f
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.
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