RFC Kernel tracing thread flag
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest20 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/20 | LTTng Kernel Trace Thread Flag Alphaarch/ | +3 | 0 replies | |
| 2/20 | LTTng Kernel Trace Thread Flag ARMarch/ arch/ | +5 | 0 replies | |
| 3/20 | LTTng Kernel Trace Thread Flag AVR32arch/ | +3 | 0 replies | |
| 4/20 | LTTng Kernel Trace Thread Flag Blackfinarch/ | +3 | 0 replies | |
| 5/20 | LTTng Kernel Trace Thread Flag Crisarch/ | +7 | 0 replies | |
| 6/20 | LTTng Kernel Trace Thread Flag Frvarch/ | +3 | 0 replies | |
| 7/20 | LTTng Kernel Trace Thread Flag H8300arch/ | +3 | 0 replies | |
| 8/20 | LTTng Kernel Trace Thread Flag ia64arch/ arch/ | +11 | 0 replies | |
| 9/20 | LTTng Kernel Trace Thread Flag m32rarch/ | +7 | 0 replies | |
| 10/20 | LTTng Kernel Trace Thread Flag m68karch/ arch/ | +4 | 0 replies | |
| 11/20 | LTTng Kernel Trace Thread Flag MIPSarch/ arch/ | +4 | 0 replies | |
| 12/20 | LTTng Kernel Trace Thread Flag pariscarch/ | +2 | 0 replies | |
| 13/20 | LTTng Kernel Trace Thread Flag powerpcarch/ | +5 | 0 replies | |
| 14/20 | LTTng Kernel Trace Thread Flag s390arch/ arch/ arch/ | +18 | 1 reply | |
| 15/20 | LTTng Kernel Trace Thread Flag SHarch/ | +7 | 1 reply | |
| 16/20 | LTTng Kernel Trace Thread Flag sparcarch/ arch/ arch/ | +8 | 0 replies | |
| 17/20 | LTTng Kernel Trace Thread Flag UMLarch/ | +2 | 0 replies | |
| 18/20 | LTTng Linux Kernel Trace Thread Flag x86arch/ arch/ | +18 | 0 replies | |
| 19/20 | LTTng Kernel Trace Thread Flag xtensaarch/ | +3 | 0 replies | |
| 20/20 | LTTng Kernel Trace Thread Flag APIinclude/ kernel/ kernel/ | +67 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC patch 00/20] Kernel tracing thread flag
This is the generalisation of the TIF_SYSCALL_FTRACE thread flag for :
- multiple tracers (even accessible from modules)
- multiple architectures
It includes :
- Addition of the TIF_KERNEL_TRACE for all Linux architectures.
- Modification of some architecture entry*.S files to ensure that the thread flag is re-read upon syscall exit to ensure that syscall exit is traced. Basically, what I try to achieve here is to make sure that given the following sequence will get its syscall exit event traced :
- Thread preempted in a system call
- Activation of all TIF_KERNEL_TRACE thread flags
- ...enough time passes to expect that all tracing sites are activated...
- syscall exit -> expected to be traced
But if the thread flags used at syscall exit are the same that has been read at syscall entry, the event will be skipped. This does not permit reaching a known "quiescent state" where we know that all tracing sites are activated.
Note that having non-perfectly matched syscall trace entry/exit may have implications wrt getname/putname refcounting for instance, and could cause problems if getname/putname was used in the syscall entry/exit pairs. We will have to deal with this somehow when we face this problem. Keeping a per-thread flag saying that a matching syscall_entry tracing has been executed could fix this problem. We could even re-use TIF_SYSCALL_FTRACE for this specific purpose.
Mathieu
Signature · 2 lines
Mathieu Desnoyers OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68