commit | 8c5e4f4e76febcf7699fdc0351553f615354f503 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Wed Oct 28 11:11:55 2020 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Nov 10 21:02:19 2020 +0000 |
tree | 6c53f045e4d3400985cb67b8bbc2cbc82f1929ef | |
parent | 61465db5edd8eca02da92eb43cbbff5e0a129216 [diff] |
Attn: Seperate handling of PHYP and Hostboot TI When attention handler has determined that a special attention was due to a TI it will use the TI info data to determine whether the TI was from PHYP or hostboot and handle the individual cases as appropriate. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I228b306da2a4e2d2a6dff1d73fb2d8401578939a
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