Messages in this thread |  | | Date | Thu, 5 Dec 2013 22:12:55 +0100 | From | Borislav Petkov <> | Subject | Re: [BUG] Re: [PATCH v10 1/3] aerdrv: Trace Event for AER |
| |
On Thu, Dec 05, 2013 at 11:21:10AM -0700, Betty Dall wrote: > The definition of the GHES_SEV* matches up with the error severity > definition of the CPER records as defined in the UEFI spec section > N.2.1: > "Indicates the severity of the error condition. The severity of > the error record corresponds to the most severe error > section. > 0 - Recoverable (also called non-fatal uncorrected) > 1 - Fatal > 2 - Corrected > 3 - Informational > All other values are reserved. > Note that severity of "Informational" indicates that the record > could be safely ignored by error handling software."
Actually, we can go even one radical step further and drop ghes_severity() completely because GHES severity in the ACPI spec 5.0 is defined almost exactly the same:
"18.3.2.6.1 Generic Error Data
...
Identifies the error severity of the reported error: 0 – Recoverable 1 – Fatal 2 – Corrected 3 – None Note: This is the error severity of the entire event. Each Generic Error Data Entry also includes its own Error Severity field."
I don't know which version of the spec dictated
enum { GHES_SEV_NO = 0x0, GHES_SEV_CORRECTED = 0x1, GHES_SEV_RECOVERABLE = 0x2, GHES_SEV_PANIC = 0x3, };
though and whether we're going to have to differentiate between the old and GHES numerical severity levels. Which, if we have to, would be very nasty...
-- Regards/Gruss, Boris.
Sent from a fat crate under my desk. Formatting is fine. -- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |