Description
Description:
Visibility into the Linux kernel has always been critical for debugging and validating the execution of the code. The never ending challenge is to be able to trace the code without causing extra overhead, as tracing is most useful in a production environment.
Possible topics for this year include:
- Updating the deferred stack tracer for sframes.
- A light weight lock stat tracer
- More read1ng of user space from syscall tracepoints
- Additions to the persistent ring buffer
- Adding error injection via trace points and kprobes
- Doing more with synthetic events
- Rewriting the histogram/trigger/synthetic event code
And much more
What has been done before
Here's the enhancements that were added to Linux tracing that were derived from the previous Tracing MC session:
- libside has been released for better user space tracepoint hooking
- Faultable system call tracepoints
- We have a new Runtime Verification maintainer!
Key Attendees:
- Steven Rostedt
- Masami Hiramatsu
- Mathieu Desnoyers
- Ian Rogers
- Gabriele Monaco
- Namhyung Kim
- Arnaldo Carvalho de Melo
- Tomas Glozar
- Peter Zijlstra
- Jens Remus
-
Mathieu Desnoyers (EfficiOS Inc.)10/6/26, 12:00โฏPM
The current situation regarding LTTng vs upstream Linux:
1) There are maintainers who push for everything to be in tree
2) There are maintainers who are proponents for no-GPL-export when there are no in-tree users
3) Most of the tracer common facilities are used by tracers which do not compile as modules (only builtin)
4) Linus Torvalds stated that LTTng will stay out of treeAs a...
Go to contribution page