commit | e5411f0f4d862fac11a9a32cac058a438ef5ed54 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Aug 04 22:41:35 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Aug 05 10:52:12 2021 -0500 |
tree | afa26640fcf6ccda6d53dba5ac8384254b85cb55 | |
parent | 3c79080bfa6e22dd10d983672569c9f6bfe37c1b [diff] |
initial function to apply RAS policies for root cause Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I6710b250ad6dcc9e9c9d81945580bfe23c0d1eab
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