Challenges of Deploying eBPF-based Tracing in Embedded Systems, and Alternatives in Embe...
summary
Micron EBU finds eBPF impractical on many embedded targets because it requires extra kernel options (BTF/trace support), toolchains like clang/LLVM or BPF tool runtimes, and can add 1.5 MB kernel increase; advanced eBPF features like the ring buffer map since 5.8 further restrict portability. A working alternative uses libtracefs/libtraceevent to attach to tracefs, parse the trace unit format, and optionally register event handlers; it deploys on older kernels but incurs userspace polling overhead reading per‑CPU ring buffers.
AI-written summary · about
chapters (9)
- 0:00Start
- 4:31BPF/eBPF
- 10:43Dependencies for eBPF-based tool compilation/deplo
- 18:11Trace with libtracefs & libtraceevent
- 19:33Configure tracefs with libtracefs API
- 21:02Trace event formal file
- 23:58Read raw buffer()
- 27:52Comparison
- 29:06Conclusion
related talks
19mDTrace and eBPF: new challenges
36mDebugging with eBPF on Arm Platforms
20mClosing Perspectives
50mIntroduction to eBPF
40mPanel Discussion: eBPF: A New Era in Cloud Infrastructure Tools
16m“Is Upstream Really Enough?” — Practical Realities of Using eBPF in Long-Term Supporte...
16mWhy Everyone Should Care About eBPF
29meBPF on the Rise - Getting Started