[lttng-modules.git] / instrumentation / syscalls / README

LTTng system call tracing

1) lttng-syscall-extractor

You need to build a kernel with CONFIG_FTRACE_SYSCALLS=y and
CONFIG_KALLSYMS_ALL=y for extraction. Apply the linker patch to get your
kernel to keep the system call metadata after boot.  Then build and load
the LTTng syscall extractor module. The module will fail to load (this
is expected). See the dmesg output for system call metadata.

2) Generate system call TRACE_EVENT().

Take the dmesg metadata and feed it to lttng-syscalls-generate-headers.sh, e.g.,
from the instrumentation/syscalls directory. See the script header for
usage example. It should be run for both the integers and pointers types.

After these are created, we just need to follow the new system call additions,
no need to regenerate the whole thing, since system calls are only appended to.
Commit	Line	Data
	1	LTTng system call tracing
	2
	3	1) lttng-syscall-extractor
	4
	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.
	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.,
	14	from the instrumentation/syscalls directory. See the script header for
	15	usage example. It should be run for both the integers and pointers types.
	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.