commit | 792f32f7073a47e2feb340514aea32c1875ad0dc | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Tue Jun 02 08:50:47 2020 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Jun 16 19:42:29 2020 +0000 |
tree | 74791a0e68a9cb947dfd659c7a8ce829974a1916 | |
parent | f480b7396f1415474b3e293f84d790e4c02d654d [diff] |
Add support for Get TI Info chipop Use the Get TI Info chipop to determine if a special attention was due to a TI or a breakpoint. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I256dcf1171c27e851032353226c174307105cd0a
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