RFC LTTng Kernel Instrumentation (Architecture Independent)
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest7 patches 15 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/7 | Include marker.h in kernel.h -- temporary, for code readabilityinclude/ | +1 | 0 replies | |
| 2/7 | LTTng instrumentation fsfs/ fs/ fs/ +4 more | +31 | 0 replies | |
| 3/7 | LTTng instrumentation ipcipc/ ipc/ ipc/ | +12 | 0 replies | |
| 4/7 | LTTng instrumentation kernelinclude/ kernel/ kernel/ +10 more | +147 | 4 replies | |
| 5/7 | LTTng instrumentation mmmm/ mm/ mm/ +1 more | +35 | 34 replies | |
| 6/7 | LTTng instrumentation netnet/ net/ net/ | +28 | 0 replies | |
| 7/7 | Add Markers Into Semaphore Primitiveslib/ | +9 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC 0/7] LTTng Kernel Instrumentation (Architecture Independent)
Hi,
I submit this instrumentation of the main kernel events using markers to the Linux community as an RFC. This is the instrumentation LTTng (Linux Trace Toolkit Next Generation, at http://ltt.polymtl.ca) uses.
In addition to this, I also have architecture dependent instrumentation for:
- traps
- system call entry/exit
- kernel thread creation
- IPC call
which I plan to submit a bit later, once these architecture independent core instrumentation patches will have been discussed.
The goal here is be be able to tell "what the kernel is doing" so we can :
- get execution traces from bug reporters easily.
- help userspace developers to understand the interactions of their programs with other processes and with the kernel.
Mathieu
Signature · 3 lines
Mathieu Desnoyers Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68