commit | 9a738f7ff5d706e931cc6aefa6436e43cf10f32b | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Nov 03 20:45:30 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Nov 04 10:33:30 2021 -0500 |
tree | aae9347e359ac58e37da6ec56d8a83e03dc09e91 | |
parent | 8de7fbe6eb72636546d0f5b363e31ab0c56f346a [diff] |
Add Guarded/Deconfigured fields to callout resolutions Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I8dcb9094a43a23c4cb7e8951a430199ddc01def5
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