Commit | Line | Data |
---|---|---|
5fee13fd MD |
1 | LTTng system call tracing |
2 | ||
3 | 1) lttng-syscall-extractor | |
4 | ||
deeaaf53 MD |
5 | You need to build a kernel with CONFIG_FTRACE_SYSCALLS=y and |
6 | CONFIG_KALLSYMS_ALL=y for extraction. Apply the linker patch to get your | |
7 | kernel to keep the system call metadata after boot. Then build and load | |
8 | the LTTng syscall extractor module. The module will fail to load (this | |
9 | is expected). See the dmesg output for system call metadata. | |
5fee13fd MD |
10 | |
11 | 2) Generate system call TRACE_EVENT(). | |
12 | ||
13 | Take the dmesg metadata and feed it to lttng-syscalls-generate-headers.sh, e.g., | |
deeaaf53 | 14 | from the instrumentation/syscalls directory. See the script header for |
eafcf0ad | 15 | usage example. It should be run for both the integers and pointers types. |
5fee13fd MD |
16 | |
17 | After these are created, we just need to follow the new system call additions, | |
18 | no need to regenerate the whole thing, since system calls are only appended to. |