commit | 3f363d4af0157340eae6b2a83ac1481b96622ebc | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Feb 10 16:20:37 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Feb 22 17:17:08 2022 -0600 |
tree | a59e2ee8f0f499e0d443d11f43dbd02e752f49ab | |
parent | 2a394cbb19cbc909e82736aa5a21172a19ae001a [diff] |
callout rule for TOD fault analysis This does not include actual callout support, just the rules when an callout is needed. The actual callouts will come in subsequent commits after adding support to query the TOD configuration registers. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I72c702a778e12ee20555f3e6dca77e0b6f023be7
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