commit | 82be3ab53ec05be6f225aef6fb25713de50fd349 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Dec 07 10:36:08 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Dec 09 14:03:34 2021 -0600 |
tree | 02e528b75022aef12592b7dff109cefe1b778804 | |
parent | b7879d3dae1264b06d8bf0277b5e71e669d30d65 [diff] |
Set guard policy based on analysis type Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I38d0a84c3f890635b102efd8315a5c180a451047
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