Skip to content

ftrace: Add task_comm support for trace_event

Zhaolei lkml 2 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v3 Latest2 patches 1 replyIn review
  2. v22 patches 19 repliesSuperseded

Changelog from the cover letter

v1->v2: Update Kconfig to select CONTEXT_SWITCH_TRACER in ENABLE_EVENT_TRACING v2->v3: v2 can solve problem that caused by config EVENT_TRACING alone,
but when CONFIG_FTRACE is off and CONFIG_TRACING is selected by other config, compile fail happened again. This version solves it.

Patches in v3 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2ftrace: Add task_comm support for trace_eventkernel/trace/Kconfig kernel/trace/trace_events.c+13 -21 reply
2/2ftrace: clean up of using ftrace_event_enable_disable()kernel/trace/trace_events.c+14 -300 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.

Read the v3 thread

Cover letter [PATCH v3 0/2] ftrace: Add task_comm support for trace_event

Hello,

Ingo pointed out that v2 patch still cause kernel compile fail:
kernel/built-in.o: In function `ftrace_event_enable_disable':
trace_events.c:(.text+0x4df08): undefined reference to tracing_stop_cmdline_record' trace_events.c:(.text+0x4df1f): undefined reference to tracing_start_cmdline_record'

It is because CONFIG_TRACING is on(But CONFIG_FTRACE is off), which compiles trace_events but leaves trace_sched_switch. (Which is different with problem that I fixed in v1->v2)

Changelog:
v1->v2: Update Kconfig to select CONTEXT_SWITCH_TRACER in ENABLE_EVENT_TRACING v2->v3: v2 can solve problem that caused by config EVENT_TRACING alone,
but when CONFIG_FTRACE is off and CONFIG_TRACING is selected by other config, compile fail happened again. This version solves it.

Thanks
Zhaolei