summaryrefslogtreecommitdiff
path: root/src/commonlib/bsd
diff options
context:
space:
mode:
authorHsuan Ting Chen <roccochen@chromium.org>2022-09-26 19:37:11 +0800
committerFelix Held <felix-coreboot@felixheld.de>2022-10-14 16:06:39 +0000
commitfec16a3574921743246bafe617659c4d73b8011f (patch)
tree5cefedff9f19012dc1f39bdda6edfdba3cdc9a33 /src/commonlib/bsd
parent4e85ec705e08c37a6e071bbb9d5f381eea018283 (diff)
util/elogtool: Add support for parsing CrOS diagnostics log
Remove the "_DEPRECATED_" tag from ChromeOS diagnostics event and add a subtype: "ELOG_CROS_DIAGNOSTICS_LOGS" under it. The data of "ELOG_CROS_DIAGNOSTICS_LOGS" (0x02) contains: * An uint8_t of subtype code * Any number of "ChromeOS diagnostics logs" events Each "ChromeOS diagnostics log" represents the result of one ChromeOS diagnostics test run. It is stored within an uint8_t raw[3]: * [23:19] = ELOG_CROS_DIAG_TYPE_* * [18:16] = ELOG_CROS_DIAG_RESULT_* * [15:0] = Running time in seconds Also add support for parsing this event. The parser will first calculate the number of runs it contains, and try to parse the result one by one. BUG=b:226551117 TEST=Build and boot google/tomato to OS, localhost ~ # elogtool list 0 | 2022-09-26 04:25:32 | Log area cleared | 186 1 | 2022-09-26 04:25:50 | System boot | 0 2 | 2022-09-26 04:25:50 | Firmware vboot info | boot_mode=Manual recovery | recovery_reason=0x2/0 (Recovery button pressed) | fw_tried=A | fw_try_count=0 | fw_prev_tried=A | fw_prev_result=Unknown 3 | 2022-09-26 04:25:50 | EC Event | Keyboard Recovery 4 | 2022-09-26 04:26:01 | Memory Cache Update | Normal | Success 5 | 2022-09-26 04:26:06 | System boot | 0 6 | 2022-09-26 04:26:07 | Firmware vboot info | boot_mode=Diagnostic | fw_tried=A | fw_try_count=0 | fw_prev_tried=A | fw_prev_result=Unknown 7 | 2022-09-26 04:26:07 | Diagnostics Mode | Diagnostics Logs | type=Memory check (quick), result=Aborted, time=0m0s | type=Memory check (full), result=Aborted, time=0m0s | type=Storage self-test (extended), result=Aborted, time=0m1s Change-Id: I02428cd21be2ed797eb7aab45f1ef1d782a9c047 Signed-off-by: Hsuan Ting Chen <roccochen@chromium.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/67834 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Julius Werner <jwerner@chromium.org>
Diffstat (limited to 'src/commonlib/bsd')
-rw-r--r--src/commonlib/bsd/include/commonlib/bsd/elog.h41
1 files changed, 39 insertions, 2 deletions
diff --git a/src/commonlib/bsd/include/commonlib/bsd/elog.h b/src/commonlib/bsd/include/commonlib/bsd/elog.h
index b49b375500..06ea5a77d5 100644
--- a/src/commonlib/bsd/include/commonlib/bsd/elog.h
+++ b/src/commonlib/bsd/include/commonlib/bsd/elog.h
@@ -306,8 +306,45 @@ struct elog_event_mem_cache_update {
#define ELOG_TYPE_MI_HR 0xb5
/* ChromeOS diagnostics-related events */
-#define ELOG_DEPRECATED_TYPE_CROS_DIAGNOSTICS 0xb6
-#define ELOG_DEPRECATED_CROS_LAUNCH_DIAGNOSTICS 0x01
+#define ELOG_TYPE_CROS_DIAGNOSTICS 0xb6
+#define ELOG_DEPRECATED_CROS_LAUNCH_DIAGNOSTICS 0x01
+#define ELOG_CROS_DIAGNOSTICS_LOGS 0x02
+/* Type codes for elog_event_cros_diag_log in ELOG_CROS_DIAGNOSTICS_LOGS */
+#define ELOG_CROS_DIAG_TYPE_NONE 0x00
+#define ELOG_CROS_DIAG_TYPE_STORAGE_HEALTH 0x01
+#define ELOG_CROS_DIAG_TYPE_STORAGE_TEST_SHORT 0x02
+#define ELOG_CROS_DIAG_TYPE_STORAGE_TEST_EXTENDED 0x03
+#define ELOG_CROS_DIAG_TYPE_MEMORY_QUICK 0x04
+#define ELOG_CROS_DIAG_TYPE_MEMORY_FULL 0x05
+/* Result codes for elog_event_cros_diag_log in ELOG_CROS_DIAGNOSTICS_LOGS */
+#define ELOG_CROS_DIAG_RESULT_PASSED 0x01
+#define ELOG_CROS_DIAG_RESULT_ERROR 0x02
+#define ELOG_CROS_DIAG_RESULT_FAILED 0x03
+#define ELOG_CROS_DIAG_RESULT_ABORTED 0x04
+
+/*
+ * ChromeOS diagnostics log format:
+ * [23:19] = ELOG_CROS_DIAG_TYPE_*
+ * [18:16] = ELOG_CROS_DIAG_RESULT_*
+ * [15:0] = Running time in seconds
+ */
+#define ELOG_CROS_DIAG_LOG_TYPE_BITS 5
+#define ELOG_CROS_DIAG_LOG_RESULT_BITS 3
+union elog_event_cros_diag_log {
+ uint8_t raw[3];
+ struct {
+ /* 5-bit type code, see ELOG_CROS_DIAG_TYPE_* above */
+ uint8_t type : ELOG_CROS_DIAG_LOG_TYPE_BITS;
+ /* 3-bit result code, see ELOG_CROS_DIAG_RESULT_* above */
+ uint8_t result : ELOG_CROS_DIAG_LOG_RESULT_BITS;
+ /*
+ * The running time of this diagnostics test item. If the
+ * running time exceeds the UINT16_MAX, it will be stored as
+ * UINT16_MAX instead.
+ */
+ uint16_t time_s;
+ } __packed;
+} __packed;
struct elog_event_extended_event {
uint8_t event_type;