| commit | 37acb2896f2341ba21e27cdb9960e0a265b5b537 | [log] [tgz] |
|---|---|---|
| author | Zane Shelley <zshelle@us.ibm.com> | Mon Jan 10 16:05:22 2022 -0600 |
| committer | Zane Shelley <zshelle@us.ibm.com> | Mon Jan 17 09:46:42 2022 -0600 |
| tree | 529d8749c865455971ae005a753408de35b20964 | |
| parent | 38501e12b6fda6bd30529f02c312053ad2772bb7 [diff] |
Move resolution callout support to service data class The resolution callout support is only accessible for service actions defined by the RAS data files. Unfortunately, this does not work for any plugins that need to make callouts as well. Therefore, the callout logic was moved to a common location that is accessible by the different classes. Change-Id: I5679c3b2e44bb039227740975cdef03c94747b3b 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