commit | f1184392e77da220d603e764eadbe946d6ddfe11 | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Fri Oct 07 15:17:22 2022 -0500 |
committer | Caleb Palmer <cnpalmer@us.ibm.com> | Thu Nov 17 10:37:39 2022 -0600 |
tree | 2529b7ec783318e6859f7d676b8e73853c39131a | |
parent | dd74a84fa7a80f0452e1f36867ab19ce6680454a [diff] |
Add RAS data parser handling for getting RAS data flags In the future we will be supporting an additional 'flags' type stored in the RAS data files for specific bits. This adds the handling to the RAS data parser to get those flags. Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com> Change-Id: Ie7889135ae7a643fec287565143a8ee7edc33777
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