commit | 62adf5c2f0923b7bb45bf7e4906722c3e7da8008 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Jan 18 21:06:50 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Jan 19 19:55:26 2022 +0000 |
tree | 3bcea7be97fba554a994729d301a88ddae9692e7 | |
parent | 19df3706d434eebf932240850b0e54cd95b49f02 [diff] |
store IsolationData in ServiceData class Instead of passing both the IsolationData and ServiceData around everywhere, store the IsolationData inside the ServiceData class so that we only need to pass around one object. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I13f02fe43ede324ba51242a16daab107bc81a678
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