Clarify definition of chip checkstop
Previously, the ATTN_TYPE_CHECKSTOP associated with a signature was
synonymous with a system checkstop event. This is certainly true for
if a processor chip checkstops. However, this is not true if a connected
OCMB chip checkstops because it is possible in some cases for a system
to recover. To differentiate an OCMB chip checkstop from a system
checkstop they were previously reported as unit checkstops. With the
addition Odyssey OCMBs, which have ability to report both chip and unit
checkstops, we decided to fix the confusion and disassociate a chip
checkstop from a system checkstop. Now the signatures will properly
report the chip attention type and the signature filtering code has been
modified to simply associate only chip checkstops from processor chips
as system checkstop attentions.
Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: Iff9822ff8c9c0ae1afe84353010e94759dbdf49d
diff --git a/test/test-root-cause-filter.cpp b/test/test-root-cause-filter.cpp
index 71d7bf2..34d80fe 100644
--- a/test/test-root-cause-filter.cpp
+++ b/test/test-root-cause-filter.cpp
@@ -43,7 +43,7 @@
// EQ_CORE_FIR[14]: ME = 0 checkstop
libhei::Signature checkstopSig{procChip0, eqCoreFir, 0, 14,
- libhei::ATTN_TYPE_CHECKSTOP};
+ libhei::ATTN_TYPE_CHIP_CS};
// MC_DSTL_FIR[1]: AFU initiated Recoverable Attn on Subchannel A
libhei::Signature reAttnSig{procChip0, mc_dstl_fir, 0, 1,