RE: [PATCH 00/12 v2] ring-buffer/tracing: Remove disabling of ring buffer while reading trace file

[David Laight]

From: Steven Rostedt
> Sent: 19 March 2020 23:22
...
> 
> This patch series attempts to satisfy that request, by creating a
> temporary buffer in each of the per cpu iterators to place the
> read event into, such that it can be passed to users without worrying
> about a writer to corrupt the event while it was being written out.
> It also uses the fact that the ring buffer is broken up into pages,
> where each page has its own timestamp that gets updated when a
> writer crosses over to it. By copying it to the temp buffer, and
> doing a "before and after" test of the time stamp with memory barriers,
> can allow the events to be saved.

Does this mean the you will no longer be able to look at a snapshot
of the trace by running 'less trace' (and typically going to the end
to get info for all cpus).

A lot of the time trace is being written far too fast for it to make
any sense to try to read it continuously.

Also, if BPF start using ftrace, no one will be able to use it for
'normal debugging' on such systems.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)