commit | 7de01130957b899128c8f413d585118e6db4115f | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Sep 28 13:29:19 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Sep 28 13:29:36 2021 -0500 |
tree | 0fcc5cc239a6176aef284493573f8c77babf56fd | |
parent | 73aa431cf80b018f3fe73f5ed7a7ea263141ced1 [diff] |
RAS action files for PEC chiplet Change-Id: I0aa805079ef23a689797d89f285913e612e00a15 Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
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