ftrace: support binary record (V2)
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 13 repliesIn review
changed from V1 from the cover letter
1) not use Python style. Formates typically have 2~8 '%', using Python style make no sense, and gcc can not check parameters when we use Python style.
2) enable ftrace trace markers.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | add binary printfinclude/ lib/ lib/ | +452 | 0 replies | |
| 2/5 | ftrace: infrastructure for supporting binary recordinclude/ kernel/ kernel/ +4 more | +238 | 9 replies | |
| 3/5 | ftrace: add ftrace_bprintk()include/ include/ include/ +3 more | +167 | 0 replies | |
| 4/5 | ftrace: show ftrace_bprintk()'s formatskernel/ kernel/ kernel/ | +88 | 4 replies | |
| 5/5 | ftrace: trace markerskernel/ kernel/ kernel/ | +249 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/5] ftrace: support binary record (V2)
Binary record will save memory in trace buffer, and more events can be recorded in buffer.
This patch add infrastructure for supporting binary record.
This infrastructure records events by binary and shows events by human readable text.
And add a API ftrace_bprintk() using this infrastructure. (This API is exactly the same as ftrace_printk(), beside it record the date by binary)
changed from V1:
1) not use Python style. Formates typically have 2~8 '%', using Python style make no sense, and gcc can not check parameters when we use Python style.
2) enable ftrace trace markers.
patches are for tracing/ftrace.
---