ftrace: port to the new ring_buffer
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest6 patches 14 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | ftrace: give time for wakeup test to runkernel/ | +3 | 0 replies | |
| 2/6 | Unified trace bufferinclude/ kernel/ kernel/ +1 more | +1807 | 3 replies | |
| 3/6 | ring_buffer: add paranoid check for buffer pagekernel/ | +11 | 0 replies | |
| 4/6 | ring_buffer: reset buffer page when freeingkernel/ | +15 | 0 replies | |
| 5/6 | ftrace: make work with new ring bufferkernel/ kernel/ kernel/ +8 more | +288 | 0 replies | |
| 6/6 | ftrace: take advantage of variable length entrieskernel/ kernel/ kernel/ +1 more | +302 | 8 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/6] ftrace: port to the new ring_buffer
These patches are against linux-tip.
The first is just a fix in the wakeup selftest.
The next is a port of the Unified tracer buffer to linux-tip and some updates.
After that is the ftrace port to use the ring buffer, followed by some more enhancements to ftrace because of the new variable length buffer.
I tried a few configurations and tried to test all the different ftrace tracers, but I'm sure there may be some bugs still to work out. I worked out all those that I found.
But, with the ring_buffer I can envision several ways to clean up ftrace and to make adding new tracers cleaner.
I'm also thinking about making a way that each tracer can allocate its own buffer, and allow for more than one tracer to be running at the same time! (only with different buffers).
-- Steve