| commit | 02d59af5419a8d262d226be4febd3e70c7942be2 | [log] [tgz] |
|---|---|---|
| author | Zane Shelley <zshelle@us.ibm.com> | Tue Feb 07 17:52:34 2023 -0600 |
| committer | Zane Shelley <zshelle@us.ibm.com> | Wed Feb 08 09:43:03 2023 -0600 |
| tree | 345d9edbcc1e05ba60379e9852e04371ac6e76c1 | |
| parent | 1ff926e0f055dde8f068d671d4df524ce54d7725 [diff] |
Exception handling with flags in ras-data-parser It is possible that a signature may not be defined in the RAS data. In which case, trying to access the flags for an undefined signature would throw an exception. This is not the desired behavior. Instead, we'll catch the exceptions and move on as if the flag is not defined. Change-Id: I4d3cff52ce5f32074fca9863f60b84726dd590aa Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
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