commit | 5f6e3deb694c0d8f4d5fa87517fdc9c260961e2b | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Feb 23 13:57:37 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Feb 23 20:42:29 2021 +0000 |
tree | 978b9cd077c8bb4694e1658282fd835a2e2eb751 | |
parent | 4bbcb38f367e58b3724768ad998e31610b38869a [diff] |
Guard support for PELs Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ib32a3ccbf165bb9a541fa37fcdaf9da4c8e63f81
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