ftrace: overrun accounting and trace_pipe headers
Status from this message: thanks, applied.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | ftrace: add logic to record overrunskernel/ kernel/ | +16 | 2 replies | |
| 2/3 | ftrace: add trace pipe header plugginkernel/ kernel/ | +36 | 2 replies | |
| 3/3 | TEST PATCH - ftrace example patch for use of trace pipe headerskernel/ | +41 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] ftrace: overrun accounting and trace_pipe headers
The first patch in this series adds accounting to record overruns. That is where the writing catches up to the reading of the buffer. This really only matters for trace_pipe since that's a consumer / producer output file.
The next patch adds new methods for the plugins to hook into the open_pipe and open_read, to let a plugin produce a header. The open_read method can also be used to do something when overruns are detected.
The last patch is a test patch AND SHOULD NOT BE APPLIED. It is just an example in how to use the new methods to produce a header. It simply makes the ftrace tracer produce a simple "Test header" before any output.
-- Steve