commit | 6a69e6e5fc726125ca5fb4b3ae4b13d6e22ba03c | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Tue Apr 05 23:18:29 2022 -0500 |
committer | Caleb N. Palmer <cnpalmer@us.ibm.com> | Tue Apr 12 16:25:41 2022 +0000 |
tree | a2d4c478c2b9ec9df0d51614bd8ae4ed05b4eec2 | |
parent | 20ed74db38b328f78e72c5fe3121a6a90d6efe01 [diff] |
Attn: Clear attention interrupts Clear attention interrupts when starting the attention handler. This code will try to clear active attention interrupts. If an attention is active the interrupt will remain active as well. This code is meant to address cases where attentions have been cleared but the associated interrupt has not been cleared. This fixes the problem of attention handler not handling attentions after an MPIPL. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: Ib0873a3afb891c49a125d2f8b00e2c621b0189e3
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