[lttng-dev] What are sys calls starting with compat?

Shariyar syed.shariyar at gmail.com
Tue Dec 10 14:39:40 EST 2013

What does sys_unknown mean and why doe it occur? Does it mean that LTTng
can not find the name of system call?


Message: 2
Date: Tue, 10 Dec 2013 15:31:19 +0000 (UTC)
From: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
To: Daniel Thibault <Daniel.Thibault at drdc-rddc.gc.ca>
Cc: lttng-dev at lists.lttng.org
Subject: Re: [lttng-dev] What are sys calls starting with compat?
        <1571110803.82672.1386689479225.JavaMail.zimbra at efficios.com>
Content-Type: text/plain; charset=utf-8

----- Original Message -----
> From: "Daniel Thibault" <Daniel.Thibault at drdc-rddc.gc.ca>
> To: lttng-dev at lists.lttng.org
> Cc: "Mathieu Desnoyers" <mathieu.desnoyers at efficios.com>
> Sent: Tuesday, December 10, 2013 9:57:21 AM
> Subject: Re: [lttng-dev] What are sys calls starting with compat?
> > Date: Tue, 10 Dec 2013 01:55:48 +0000 (UTC)
> >
> > System calls with "compat" prefix are for e.g. 32-bit processes running
> > a 64-bit kernel:
> > those processes are using a different system call table (ia32 for Intel)
> > than 64-bit processes,
> > and therefore those system calls are named "compat_*" by LTTng.
> >
> > Mathieu
>    I presume the LTTng event names will also be prefixed with "compat_".


>  For
>    instance, "compat_sys_rmdir".


>  Or would it be "sys_compat_rmdir"?


>  And
>    what of the exit_syscall and sys_unknown events?

exit_syscall has no compat prefix as I recall.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20131210/850c26bc/attachment.html>

More information about the lttng-dev mailing list