<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kernel-Tracing on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/kernel-tracing/</link>
    <description>Recent content in Kernel-Tracing on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 25 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/kernel-tracing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux Kernel Dynamic Tracing: trace-cmd vs SystemTap vs perf probe</title>
      <link>https://www.pistack.xyz/posts/2026-05-25-linux-kernel-dynamic-tracing-trace-cmd-vs-systemtap-vs-perf-probe-guide/</link>
      <pubDate>Mon, 25 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-25-linux-kernel-dynamic-tracing-trace-cmd-vs-systemtap-vs-perf-probe-guide/</guid>
      <description>&lt;p&gt;Kernel dynamic tracing allows you to observe running Linux systems in real time — probing kernel functions, tracking system calls, measuring latency, and diagnosing performance bottlenecks without recompiling the kernel or restarting services. Three major toolchains dominate this space: &lt;strong&gt;trace-cmd&lt;/strong&gt; (the ftrace frontend), &lt;strong&gt;SystemTap&lt;/strong&gt; (Red Hat&amp;rsquo;s scripting-based tracer), and &lt;strong&gt;perf probe&lt;/strong&gt; (the perf subsystem&amp;rsquo;s dynamic instrumentation interface).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
