commit | 2f92130c7964a286a1e76df938e36bc21ad8033d | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Aug 09 13:23:25 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Aug 10 16:32:33 2021 -0500 |
tree | 064ab72f74d15aa48d63095b5e76efc3b1885877 | |
parent | ca49619871ab7f914dbd4b939fe81851cb927dc9 [diff] |
Refined guard type in HardwareCalloutResolution A resolution guard type needs to be evaluated during the resolve() function and not when the resolution is created. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ia597ed93567b27c2cd9423f6fb0f7e75158fc315
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