commit | 39fcf65dce4d91601951c146a543bf85d68f6b3c | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Tue Oct 19 20:38:29 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Nov 02 21:47:09 2021 +0000 |
tree | e8216429c68459b912d8381909bf6563a413a491 | |
parent | d6af0b1c23568905589293df240568199ce90d9d [diff] |
Attn: Qualify MPIPL request with dump policy Check the value of the dumpPolicyEnabled property and if it is true (dumps enabled) then request MPIPL for PHYP TI cases, otherwise quiesce the host. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: Iff9d89c18b37fff02b741c20b9f988238674a147
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