commit | e4bfb47cacbab517d15ad965174fc04368742df7 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Aug 10 12:47:32 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Aug 10 22:17:32 2021 -0500 |
tree | f5ae78b9551607699079dd3b6e965352698a170f | |
parent | 7698b304a6e778c15f73f724bb8e05f18e3052e8 [diff] |
Add RAS data support for 'callout_self' and 'callout_unit' With this change, 'callout_self' and 'callout_unit' actions will add a callout with location code into the PEL. Change-Id: I975f2059a71f7b529a40fae03273cc3c387c4cef 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