commit | 0b8368cb0aa251032eb18b5c938d009e27f0b152 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Mar 18 17:33:41 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Mar 18 17:33:41 2021 -0500 |
tree | 9e9995e8940642e645cd2bc74eab4ab191f489c6 | |
parent | 1d29e5c7da9aad5c3a2ea63a9fa4b5da7c6bd75e [diff] |
Initial classes for callout resolutions Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I5df0c1cc59facc5c36aac20ca52503d20ae0f76a
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