clang-format: re-format for clang-18

clang-format-18 isn't compatible with the clang-format-17 output, so we
need to reformat the code with the latest version. The way clang-18
handles lambda forma

clang-format: re-format for clang-18

clang-format-18 isn't compatible with the clang-format-17 output, so we
need to reformat the code with the latest version. The way clang-18
handles lambda formatting also changed, so we have made changes to the
organization default style format to better handle lambda formatting.

See I5e08687e696dd240402a2780158664b7113def0e for updated style.
See Iea0776aaa7edd483fa395e23de25ebf5a6288f71 for clang-18 enablement.

Change-Id: I1d204ff0a167c43688f2217e9dee5504c71cd4f0
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...

clang-format: copy latest and re-format

clang-format-16 has some backwards incompatible changes that require
additional settings for best compatibility and re-running the formatter.
Copy the latest

clang-format: copy latest and re-format

clang-format-16 has some backwards incompatible changes that require
additional settings for best compatibility and re-running the formatter.
Copy the latest .clang-format from the docs repository and reformat the
repository.

Change-Id: I27b0d1357211259edb6ec2776924729052f238d6
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...

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 chec

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

show more ...

Avoid guarding on TOD interfaces errors

The error could be anywhere between the two processors in the interface.
Fatally guarding the MDMT will cause system outage until service is
done. Instead, do

Avoid guarding on TOD interfaces errors

The error could be anywhere between the two processors in the interface.
Fatally guarding the MDMT will cause system outage until service is
done. Instead, do not guard on the TOD interface errors to avoid outage.

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I446917bad985e5143657398b2fbadacf6e8c4a9d

show more ...

Hardware analysis support of TOD failures

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I8e2659cc832113e05c99b8dd091757bcab3dcdea

callout rule for TOD fault analysis

This does not include actual callout support, just the rules when an
callout is needed. The actual callouts will come in subsequent commits
after adding support t

callout rule for TOD fault analysis

This does not include actual callout support, just the rules when an
callout is needed. The actual callouts will come in subsequent commits
after adding support to query the TOD configuration registers.

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I72c702a778e12ee20555f3e6dca77e0b6f023be7

show more ...

Add support for TOD clock callouts

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I42726f6d1b036120fcfe217e6dd47be8dd6d927b