commit | c49d20b960b385ec641bd57ca5c1946b55ff2ea6 | [log] [tgz] |
---|---|---|
author | austinfcui <austinfcui@gmail.com> | Tue Feb 22 16:36:47 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Mar 11 21:19:55 2022 +0000 |
tree | cf0bcd415dde5bb1baab99803d7773dd91385c14 | |
parent | ac5bd05ceaf76afafe0bb2e825b749f6d0fa95d6 [diff] |
attn PEL additional-data map access cleanup Signed-off-by: austinfcui <austinfcui@gmail.com> Change-Id: Ic5b167ee45a31bc16bb5d30e95dced2a72818e77
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