-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle APML_ALERT assertion for SBRMI::[AlertSts] #103
base: main
Are you sure you want to change the base?
Conversation
1. If there is core poison consumption error occured, the APML_ALERT will be toggled low, and no one to clear it to de-assert APML_ALERT. This commit clears the RMI_ALERTSTATUS [0x10 ~ 0x1f] [0x50 ~ 0x5f] which will clear the SBRMI::[AlertSts] bit and de-assert APML_ALERT. 2. Incremented the minor version by one to indicate there is a code change to ADDC for v14 release. 3. Handled error case if the family is not Turin/Genoa. Signed-off-by: Abinaya Dhandapani <[email protected]>
static_cast<uint32_t>(buffer)); | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No cations required in case of read_register failure?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In case of write failure , it will logged in the write_register() API.
So we dont require it to be logged here. Also we continue the ADDC functionality even if the write_register() call fails.
|
||
if (ret == OOB_SUCCESS) | ||
{ | ||
if ((buffer & 0x0F) != 0) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
magic number: 0x0F
"Socket%d: MCE Stat of SBRMIx[0x%x] is set to 0x%x\n", | ||
socNum, alert_status[i], buffer); | ||
|
||
buffer = buffer & 0xFF; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
magic number 0xFF
If there is core poison consumption error occured, the APML_ALERT will be toggled low, and no one to clear it to de-assert APML_ALERT. This commit clears the RMI_ALERTSTATUS [0x10 ~ 0x1f] [0x50 ~ 0x5f] which will clear the SBRMI::[AlertSts] bit and de-assert APML_ALERT.
Incremented the minor version by one to indicate there is a code change to ADDC for v14 release.
Handled error case if the family is not Turin/Genoa.