Re: [RFC PATCH v4 9/9] printk: use a new ringbuffer implementation

[Steven Rostedt]

On Thu, 8 Aug 2019 16:33:20 -0700
Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:


> To which the obvious solution is "just use a different buffer for the
> next boot". But that brings up the *second* big issue with a
> reboot-safe buffer: it can't just be anywhere. Not only do you have to
> have some way to find the old one, the actual location may end up
> being basically fixed by hardware or firmware.

Could we possibly have a magic value in some location that if it is
set, we know right away that the buffer here has data from the last
reboot, and we read it out into a safe location before we start using
it again?

-- Steve