commit | 236bb730eb4957f9b506e61b2ab086b4b5b663ac | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Mar 24 17:07:46 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Mar 26 16:25:34 2021 +0000 |
tree | daefb5ffab8c172642e629d0c8cfb18fe7ad76e0 | |
parent | 063f6bdc3957d65e127a4616a3d04c9f054c0e5f [diff] |
Implemented HardwareCalloutResolution::resolve() Change-Id: I19a0d1da6b172fd74fab8680c515391b883dac95 Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
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