summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAaron Durbin <adurbin@chromium.org>2016-08-03 17:32:47 -0500
committerMartin Roth <martinroth@google.com>2016-08-08 18:40:18 +0200
commit36fdec88e60a2887c2e46a273de5246174193259 (patch)
tree6c134a7322fbe70363be25530b2630364bfe387f
parent9b0a3430593ef579322816377440d76d914e090c (diff)
downloadcoreboot-36fdec88e60a2887c2e46a273de5246174193259.tar.xz
drivers/elog: use event region size when adding a clear event
For the elog shrink case we log the number of bytes shrunk from the event log. However, when clearing the log the size recorded was the entire region size including the header as well as the event region space. To be more consistent mark the clearing event with the number of bytes actually cleared out (excluding the header size). BUG=chrome-os-partner:55932 Change-Id: I7c33da97bd29a90bfe975b1c6f148f181016f13f Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: https://review.coreboot.org/16092 Tested-by: build bot (Jenkins) Reviewed-by: Furquan Shaikh <furquan@google.com>
-rw-r--r--src/drivers/elog/elog.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/drivers/elog/elog.c b/src/drivers/elog/elog.c
index 6eacba56c7..59bc1de8d9 100644
--- a/src/drivers/elog/elog.c
+++ b/src/drivers/elog/elog.c
@@ -469,7 +469,7 @@ int elog_clear(void)
return -1;
/* Log the clear event */
- elog_add_event_word(ELOG_TYPE_LOG_CLEAR, total_size);
+ elog_add_event_word(ELOG_TYPE_LOG_CLEAR, log_size);
return 0;
}
@@ -576,7 +576,7 @@ int elog_init(void)
/* Log a clear event if necessary */
if (event_count == 0)
- elog_add_event_word(ELOG_TYPE_LOG_CLEAR, total_size);
+ elog_add_event_word(ELOG_TYPE_LOG_CLEAR, log_size);
#if !defined(__SMM__)
/* Log boot count event except in S3 resume */