commit | a029985855c68d3d8a2be9b5924e873f681fcb05 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Fri Nov 13 13:38:04 2020 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Nov 18 02:23:10 2020 +0000 |
tree | da9ad83bc92b94c434ee047360812fa8131736ac | |
parent | f4bd5ff699132a919b0547738f7a1b0cc4f7b642 [diff] |
util::pdbg functions for path, position, and target type Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I4f4a5b1aa6ab13f60e61d77a866cfc24c7854677
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