RFC TIF_KERNEL_TRACE thread flags
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest21 patches 6 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/21 | LTTng Kernel Trace Thread Flag Alphaarch/ | +3 | 0 replies | |
| 2/21 | LTTng Kernel Trace Thread Flag ARMarch/ | +3 | 1 reply | |
| 3/21 | LTTng Kernel Trace Thread Flag AVR32arch/ | +3 | 0 replies | |
| 4/21 | LTTng Kernel Trace Thread Flag Blackfinarch/ | +3 | 0 replies | |
| 5/21 | LTTng Kernel Trace Thread Flag Crisarch/ | +7 | 0 replies | |
| 6/21 | LTTng Kernel Trace Thread Flag Frvinclude/ | +3 | 0 replies | |
| 7/21 | LTTng Kernel Trace Thread Flag H8300arch/ | +3 | 0 replies | |
| 8/21 | LTTng Kernel Trace Thread Flag ia64arch/ arch/ | +11 | 0 replies | |
| 9/21 | LTTng Kernel Trace Thread Flag m32rinclude/ | +7 | 0 replies | |
| 10/21 | LTTng Kernel Trace Thread Flag m68karch/ arch/ | +4 | 0 replies | |
| 11/21 | LTTng Kernel Trace Thread Flag MIPSarch/ | +3 | 0 replies | |
| 12/21 | LTTng Kernel Trace Thread Flag pariscarch/ | +2 | 0 replies | |
| 13/21 | LTTng Kernel Trace Thread Flag powerpcarch/ | +5 | 0 replies | |
| 14/21 | LTTng Kernel Trace Thread Flag s390arch/ | +2 | 0 replies | |
| 15/21 | LTTng Kernel Trace Thread Flag SHarch/ | +7 | 0 replies | |
| 16/21 | LTTng Kernel Trace Thread Flag sparcarch/ | +2 | 0 replies | |
| 17/21 | LTTng Kernel Trace Thread Flag sparc64arch/ | +2 | 0 replies | |
| 18/21 | LTTng Kernel Trace Thread Flag UMLarch/ | +2 | 0 replies | |
| 19/21 | LTTng Linux Kernel Trace Thread Flag x86arch/ arch/ | +8 | 2 replies | |
| 20/21 | LTTng Kernel Trace Thread Flag xtensaarch/ | +3 | 0 replies | |
| 21/21 | LTTng Kernel Trace Thread Flag APIinclude/ kernel/ kernel/ | +67 | 3 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC patch 00/21] TIF_KERNEL_TRACE thread flags
Hello,
This is the implementatino of TIF_KERNEL_TRACE thread flags I did in the LTTng tree. Basically, it offers :
- Setting a per-thread flag for _all_ threads to enable system-wide syscall tracing.
- No performance impact when disabled, no need to stop threads upon activation/deactivation (does not add latency to userspace threads upon activation).
The most tricky bits are in the x86_64 architecture, because its entry_64.S code does not expect the thread flags to be changed concurrently while the thread is running. I modified entry_64.S so that the architecture does not suffer of any performance impact when syscall audit or secure computing is enabled, but tests for the TIF_KERNEL_TRACE flag upon return to userspace too.
Given this looks very much like what Frederic is currently doing, I think it's good to post it for comments.
utrace tracehooks could potentially make this patchset obsolete, but I an not yet convinced that utrace offers the same low-latency guarantees as this code.
It applies on top of kernel 2.6.29-rc7.
Mathieu
Signature · 2 lines
Mathieu Desnoyers OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68