| commit | 36fdec88e60a2887c2e46a273de5246174193259 | |
| author | Aaron Durbin <adurbin@chromium.org> | |
| Wed, 3 Aug 2016 22:32:47 +0000 (3 17:32 -0500) | ||
| committer | Martin Roth <martinroth@google.com> | |
| Mon, 8 Aug 2016 16:40:18 +0000 (8 18:40 +0200) | ||
| tree | 6c134a7322fbe70363be25530b2630364bfe387f | treesnapshot (tar.gz zip) |
| parent | 9b0a3430593ef579322816377440d76d914e090c | commitdiff |
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>
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>
| src/drivers/elog/elog.c | diffblobblamehistory |