commit | d28d5f8b6d6a6122a06c285b6841ba2a46d9267f | [log] [tgz] |
---|---|---|
author | austinfcui <austinfcui@gmail.com> | Thu Apr 28 16:20:39 2022 -0500 |
committer | austinfcui <austinfcui@gmail.com> | Mon May 02 15:12:40 2022 -0500 |
tree | 2a9492778d1750ffed9894d842063c7cba37c879 | |
parent | e81eb15d93922a1ce9dd1362fe06af6e2523f416 [diff] |
Add Attn config option for clearing Attn Interrupts Added attn config option Added UT for attn config object Added UT for cli that uses attn config object Signed-off-by: austinfcui <austinfcui@gmail.com> Change-Id: I0e30ebf4d94de676814bf5e173691c4d1ee362cb
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