commit | 9513582b8748fe2566ff451c2a2514e079dd56fb | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Aug 23 09:00:05 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Aug 23 10:18:10 2021 -0500 |
tree | b72b62e9d415356d15c0e4fab3d2d3527ae3a672 | |
parent | c85716ca7532aded52285f91ce4741091f77cdb5 [diff] |
Simplified Guard class and supporting functions Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I7a4b2298198c7aa9434c08dfa949081ed6437a53
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