commit | bf3326fb84b86edecf8c20b46c548240bda4b980 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Fri Nov 12 13:41:39 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Nov 15 18:05:28 2021 +0000 |
tree | 90e0d42027093cc74c40b303bdb4c9c317385c5a | |
parent | 135793a84b6631127d791757f5003f8b54ccf472 [diff] |
Enable guard support Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I7bc6c0cdd3aa6d513f1a87d351b99069fc005339
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