commit | 6a62e40dc7cfe649a5dd3209097f3ec6fd93f4e4 | [log] [tgz] |
---|---|---|
author | austinfcui <austinfcui@gmail.com> | Wed Dec 01 11:52:45 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Dec 08 17:34:42 2021 +0000 |
tree | 9eba1538863f864453abf1f40bdbb555ae358f20 | |
parent | 611b344212fe92f73b74dfe212c9029841549068 [diff] |
Add PDBG callback function for logging with log level Signed-off-by: austinfcui <austinfcui@gmail.com> Change-Id: I8cac38dec0d2f48ef20d89c95e77f73079fd31d6
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