X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=instrumentation%2Fsyscalls%2FREADME;h=1e9bec49c5e3a207fb5597030f6657e147d97069;hb=31c77635394eb16a84e467ced6cb35b23d491ece;hp=4b857994be64e1547072872b36c6ccaf453d81b5;hpb=5fee13fdbe001aacbdd61052f2ab0be57bfd6c5f;p=lttng-modules.git

diff --git a/instrumentation/syscalls/README b/instrumentation/syscalls/README
index 4b857994..1e9bec49 100644
--- 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. 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.