RFC Improvements to ftrace comm[] handling
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 10 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | tracing: Embed 'char comm[16]' in a structurekernel/ kernel/ kernel/ +5 more | +75 | 2 replies | |
| 2/2 | tracing: Keep pid and comm[] in the same structurekernel/ | +39 | 8 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH rfc 0/2] Improvements to ftrace comm[] handling
RFC because they are untested and I want to send them before going on holiday for 2 weeks (should still have email access).
The first patch avoids a lot of 'potentially unsized' string functions by embedding the char[] use to hold task->comm[] in a structure.
The second adjsuts the data structure used to cache the task names in the thread switch code.
David Laight (2):
tracing: Embed 'char comm[16]' in a structure
tracing: Keep pid and comm[] in the same structure
kernel/trace/blktrace.c | 28 +++---- kernel/trace/trace.c | 3 +- kernel/trace/trace.h | 9 ++- kernel/trace/trace_events_filter.c | 2 +- kernel/trace/trace_events_hist.c | 26 +++--- kernel/trace/trace_functions_graph.c | 10 +-- kernel/trace/trace_output.c | 24 +++--- kernel/trace/trace_sched_switch.c | 113 ++++++++++++--------------- 8 files changed, 101 insertions(+), 114 deletions(-)
Signature · 1 line
2.39.5