sal record header concern

From: xb <xavier.bru_at_bull.net>
Date: 2005-12-12 21:02:54
Hello Keith and all

It seems there is a concern around the SAL record header:
     SEVERITY item is defined as a 8 bits item in SAL documentation 
($B.2.1 rev december 2003), but as an u16 in sal.h.
This has the side effect that current code in mca.c does not call 
ia64_sal_clear_state_info() upon receiving corrected platform errors 
(priority is reported as 258 instead of 2).


--- linux-2.6.12.6/include/asm-ia64/sal.h~    2005-08-29 
18:55:27.000000000 +0200
+++ linux-2.6.12.6/include/asm-ia64/sal.h    2005-12-12 
10:19:17.000000000 +0100
@@ -320,7 +320,8 @@
 typedef struct sal_log_record_header {
     u64 id;                /* Unique monotonically increasing ID */
     sal_log_revision_t revision;    /* Major and Minor revision of 
header */
-    u16 severity;            /* Error Severity */
+    u8 severity;            /* Error Severity */
+    u8 validation_bits;        /* Validation Bits */
     u32 len;            /* Length of this error log in bytes */
     sal_log_timestamp_t timestamp;    /* Timestamp */
     efi_guid_t platform_guid;    /* Unique OEM Platform ID */


-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Received on Mon Dec 12 21:01:55 2005

This archive was generated by hypermail 2.1.8 : 2005-12-12 21:02:02 EST