[ltt-dev] Support for detailed system calls added to LTTng 2.0

[Mathieu Desnoyers]

Hi,

I added support for detailed system call output to LTTng 2.0 this week
(in the git tree head). Example usage (only for x86 32- and 64-bit
currently):

(for module and tools installation, see http://lttng.org/lttng2.0)
lttng create
lttng enable-event -a -k --syscall
lttng start
...
lttng destroy
babeltrace -n /root/lttng-traces/auto-20110927-213412
timestamp =  91476330032, name = sys_poll, stream.packet.context = { cpu_id = 0
+}, event.fields = { ufds = 0x7F498D134EA0, nfds = 2, timeout_msecs = -1 }
timestamp =  91476333810, name = exit_syscall, stream.packet.context = { cpu_id
+= 0 }, event.fields = { ret = 1 }
timestamp =  91476334692, name = sys_recvmsg, stream.packet.context = { cpu_id =
+0 }, event.fields = { fd = 15, msg = 0x7F498D134DE0, flags = 0 }
timestamp =  91476339817, name = exit_syscall, stream.packet.context = { cpu_id
+= 0 }, event.fields = { ret = 4120 }
timestamp =  91476359570, name = sys_open, stream.packet.context = { cpu_id = 0
+}, event.fields = { filename =
+"/root/lttng-traces/auto-20110927-213412/kernel/metadata", flags = 577, mode =
+511 }
....

The result is now _very_ useful :-)

For those who have access to hardware other than x86 32/64, I would need
the output of the lttng-syscalls-extractor from the lttng-modules 2.0
git tree. See instrumentation/syscalls/README for details. I'll be able
to automatically generate per-architecture syscall tracing headers from
the dmesg output produced.

Thanks !

Mathieu

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com