Skip to content

tracing: Tracing integration - dynamic ftrace for SystemTap

Atsushi Tsuji lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 15 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2tracing: Fix minor bugs for __unregister_ftrace_function_probekernel/trace/ftrace.c+2 -22 replies
2/2tracing: Export ftrace API for kernel moduleskernel/trace/ftrace.c+2 -08 replies

Reviews trailers per patch

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

Read the v1 thread

Cover letter [PATCH 0/2] tracing: Tracing integration - dynamic ftrace for SystemTap

Hi,

Currently, there are some tracers using in Linux. Each of them are developed for different users and situations.

Ftrace has own probe mechanism, dynamic ftrace, and various plugins, and it can be used without particular userland tools. It is suitable for kernel developer. The performance counters have own userland tool merged in the kernel tree and it's easy to trace kernel events by using this tool. It is suitable for people who don't have enough knowledge of internal kernel. SystemTap has own scripting language and users can gather kernel internal information suited to their needs by customizing the script. Since it also has features, the log rotation and the initscript, to keep collecting information continually, it is suitable for system administrator and enterprise users.

I think we need to use those tracers as the situation demands, since no tracer exists to meet anyone's needs and to fit any situation. Then, we should consider the tracing mechanisms (kprobe, dynamic ftrace and etc. kernel tracing features) and tracers (user interface) separately, and all tracers should be able to use each tracing mechanisms.

The mechanism of dynamic ftrace is useful for all tracers. However only ftrace can currently use it. I think it can be used for other tracers via register_ and unregister_ftrace_function_probe function. By using it, the overhead of instrumentation can be reduced and gathering information, which cannot be traced because of a large overhead, become available. Also it can enable the performance counters to count events for all kernel functions.

First, I sent patches to integrate ftrace and SystemTap by just exporting ftrace API. Also I fixed minor bugs for __unregister_ftrace_function_probe.

The patches doesn't contain the performance counters integration, since it is still in development. I think following implementations are needed:
- add new type to perf_id (like PERF_TYPE_FTRACE)
- add event ids to struct dyn_ftrace
- add interfaces to reference event ids by user (via debugfs?)
- add probe function to count ftrace events (call do_perf_swcounter_event)

Those patches are for -tip tree.

Thanks,
Atsushi

---
 kernel/trace/ftrace.c |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)