0 views collected around this technical thread.
This article provides a comprehensive guide to Linux's ftrace tool, explaining its purpose, various tracers, how to set up and use it via debugfs, detailed command examples, implementation details, practical use cases for performance tuning and debugging, and a comparison with other tracing utilities.
This article provides a comprehensive overview of Linux kernel tracing mechanisms—including probes, tracepoints, kprobes, uprobes, and ftrace—explaining their principles, implementation details, practical tools, and real‑world case studies for performance optimization, fault diagnosis, and security monitoring.
This article provides a comprehensive overview of ftrace, explaining its architecture, tracer types, configuration steps, and practical usage examples for debugging, performance analysis, and kernel development on Linux systems.
This article explains the Linux kernel ftrace architecture, covering ring buffer principles and code, tracer implementations (function, function_graph, irq_off), trace events, dynamic and static instrumentation, and kprobe mechanisms, illustrating how tracing is integrated, managed, and optimized for various execution contexts.
This article provides an in‑depth overview of the Linux kernel ftrace tracing tool, explaining its architecture, components, configuration steps, various tracers, and practical examples for performance analysis, debugging, and system behavior monitoring.
The article details how Linux’s function‑graph ftrace tracer works on ARM64, explaining required kernel configs, how -pg inserts _mcount calls, the runtime patching of ftrace_graph_caller, register usage for argument passing, and return handling, and why shadow‑call‑stack must be disabled to enable precise call‑graph and timing analysis.
This article explains how Linux tracing tools such as kprobes, uprobes, tracepoints, eBPF, perf, ftrace, sysdig, SystemTap and LTTng fit together, describing their data sources, collection mechanisms and front‑ends, and offers guidance on choosing the right tool for low‑overhead debugging and performance analysis.