commit | 444fa1c0249320eb734150156534c0283942fe1a | [log] [tgz] |
---|---|---|
author | austinfcui <austinfcui@gmail.com> | Tue Feb 08 10:20:37 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Feb 21 17:32:12 2022 +0000 |
tree | 9a0f3918b78fd4134f428fef35f5bbbdec87ecbd | |
parent | c9e2db5e277bb69f10c75f970d435df412639842 [diff] |
Attention handler stringstream refactor Signed-off-by: austinfcui <austinfcui@gmail.com> Change-Id: Ifaacbe18aa87d73a5fd907cb8682c42726b040cc
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