tree d97b95edc4cd0eaa6b09d702af630504d0424810
parent 93b001c5c088d81d96a4b0c6f167f358f9a7c8f0
author Zane Shelley <zshelle@us.ibm.com> 1680817082 -0500
committer Zane Shelley <zshelle@us.ibm.com> 1680819784 -0500

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