commit | cb457383554b894951daa3c016f6f0c2445848b1 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Nov 02 20:55:06 2020 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Jan 06 15:24:56 2021 -0600 |
tree | 520a0df8e1ca2c23ab71355f2451deb61b4ef8a0 | |
parent | e8b2aed352f7874e73bac047c0eda228cec2e7cc [diff] |
Restructure signature filter in analyzer Change-Id: I49837b097f990cc717558e54ab700aa4f56f5d8e 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