Add x86-32 syscall headers

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

diff --git a/instrumentation/syscalls/README b/instrumentation/syscalls/README
index 4b857994be64e1547072872b36c6ccaf453d81b5..6c235e150d46af6ea59686a6fe6da30e40d95b1b 100644 (file)
--- a/instrumentation/syscalls/README
+++ b/instrumentation/syscalls/README
@@ -2,17 +2,17 @@ LTTng system call tracing
 
 1) lttng-syscall-extractor
 
-You need to build a kernel with CONFIG_FTRACE_SYSCALLS=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.
+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:
-
-sh lttng-syscalls-generate-headers.sh 3.0.4 x86-64-syscalls-3.0.4
+from the instrumentation/syscalls directory. See the script header for
+usage example.
 
 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.