summaryrefslogtreecommitdiff
path: root/util/kconfig/qconf.cc
diff options
context:
space:
mode:
authorJulius Werner <jwerner@chromium.org>2017-02-02 17:32:00 -0800
committerJulius Werner <jwerner@chromium.org>2017-04-20 00:29:07 +0200
commitd67c6876b521d784e38ea91b5a1828a24c9cb1c8 (patch)
tree7dcf7baa1f5a1b11361eadef2d3b28ef42e05c18 /util/kconfig/qconf.cc
parent2d35809530c5112276f713328bf964662488f793 (diff)
Turn CBMEM console into a ring buffer that can persist across reboots
This patch allows the CBMEM console to persist across reboots, which should greatly help post factum debugging of issues involving multiple reboots. In order to prevent the console from filling up, it will instead operate as a ring buffer that continues to evict the oldest lines once full. (This means that if even a single boot doesn't fit into the buffer, we will now drop the oldest lines whereas previous code would've dropped the newest lines instead.) The console control structure is modified in a sorta backwards-compatible way, so that new readers can continue to work with old console buffers and vice versa. When an old reader reads a new buffer that has already once overflowed (i.e. is operating in true ring buffer mode) it will print lines out of order, but it will at least still print out the whole console content and not do any illegal memory accesses (assuming it correctly implemented cursor overflow as it was already possible before this patch). BUG=chromium:651966 TEST=Rebooted and confirmed output repeatedly on a Kevin and a Falco. Also confirmed correct behavior across suspend/resume for the latter. Change-Id: Ifcbf59d58e1ad20995b98d111c4647281fbb45ff Signed-off-by: Julius Werner <jwerner@chromium.org> Reviewed-on: https://review.coreboot.org/18301 Tested-by: build bot (Jenkins) Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Diffstat (limited to 'util/kconfig/qconf.cc')
0 files changed, 0 insertions, 0 deletions