commit | 87cd2f5767321bfa88c104f32cd08c9386fb468a | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Dec 02 10:09:58 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Dec 02 10:09:58 2021 -0600 |
tree | f852ed65f16259dac1d3bdec9c7a9aee45f1c688 | |
parent | c18ba8fbf7a9d73952157a308c7d4b1418f3365a [diff] |
RAS data: add callouts for PEC targets Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: If7f613e57e636cfe2fe1dc5d3c9fa78d6b8ee38c
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