• Steven Rostedt (VMware)'s avatar
    tracing: Save off entry when peeking at next entry · ff895103
    Steven Rostedt (VMware) authored
    In order to have the iterator read the buffer even when it's still updating,
    it requires that the ring buffer iterator saves each event in a separate
    location outside the ring buffer such that its use is immutable.
    
    There's one use case that saves off the event returned from the ring buffer
    interator and calls it again to look at the next event, before going back to
    use the first event. As the ring buffer iterator will only have a single
    copy, this use case will no longer be supported.
    
    Instead, have the one use case create its own buffer to store the first
    event when looking at the next event. This way, when looking at the first
    event again, it wont be corrupted by the second read.
    
    Link: http://lkml.kernel.org/r/20200317213415.722539921@goodmis.orgSigned-off-by: default avatarSteven Rostedt (VMware) <rostedt@goodmis.org>
    ff895103
trace_output.c 30.8 KB