UPSTREAM: 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 BRANCH=None TEST=None Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: https://review.coreboot.org/16092 Reviewed-by: Furquan Shaikh <furquan@google.com> Change-Id: I7c33da97bd29a90bfe975b1c6f148f181016f13f Reviewed-on: https://chromium-review.googlesource.com/368283 Commit-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org>
This commit is contained in:
parent
d916b6aab1
commit
145d857af1
1 changed files with 2 additions and 2 deletions
|
|
@ -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 */
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue