commit | c7026261bb05cc509b0c7fb204ba967419a8b35d | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Feb 22 16:37:36 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Feb 24 19:47:00 2022 +0000 |
tree | a219f263e306127739f39ef7574aae3d1d5d6372 | |
parent | 3f363d4af0157340eae6b2a83ac1481b96622ebc [diff] |
Add simulated SCOM/CFAM read support for test Change-Id: I615f1819cd309528735d63f2e6e4b4181c58fd34 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