linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: OSDepend <osdepend@gmail.com>
Cc: linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: Issue about raw_syscalls!
Date: Tue, 16 Apr 2013 09:53:14 -0700	[thread overview]
Message-ID: <516D81FA.7080302@gmail.com> (raw)
In-Reply-To: <201304162317193846964@gmail.com>

On 4/16/13 8:17 AM, OSDepend wrote:
> Hi all,
>
> I recently use perf "-e  raw_syscalls:sys_enter  -e raw_syscalls:sys_exit" to trace all the syscall entry and exit.
> After i perf script the data, I get result like below:
>              perf 10258 [013] 260748.823215: sys_exit: NR 0 = 0
>              perf 10258 [013] 260748.823244: sys_enter: NR 59 (7fffd5b085bf, 7fffd5b0bb10, 12f7030, 3266018240, 65726f632d667265, 2811)
>              perf 10258 [013] 260748.823280: sys_exit: NR 59 = -2
>              perf 10258 [013] 260748.823283: sys_enter: NR 59 (7fffd5b085b9, 7fffd5b0bb10, 12f7030, 3266018240, 6e69622f75706363, 2811)
>           runspec 10258 [019] 260748.823995: sys_exit: NR 59 = 0
>           runspec 10258 [019] 260748.824028: sys_enter: NR 12 (0, 41b590, 0, 64, 7fffa13ff000, 37f)
>           runspec 10258 [019] 260748.824031: sys_exit: NR 12 = 7761920
>           runspec 10258 [019] 260748.824139: sys_enter: NR 9 (0, 1000, 3, 22, ffffffff, 0)
>           runspec 10258 [019] 260748.824147: sys_exit: NR 9 = 140288080863232
>           runspec 10258 [019] 260748.824167: sys_enter: NR 21 (326521cb00, 4, 3265200158, 0, 0, 0)
>           runspec 10258 [019] 260748.824187: sys_exit: NR 21 = -2
>           runspec 10258 [019] 260748.824203: sys_enter: NR 2 (326521b181, 0, 1, 0, fefefefefefefeff, 0)
>           runspec 10258 [019] 260748.824223: sys_exit: NR 2 = 4
>           runspec 10258 [019] 260748.824225: sys_enter: NR 5 (4, 7fffa135d310, 7fffa135d310, 0, fefefefefefefeff, 0)
>           runspec 10258 [019] 260748.824229: sys_exit: NR 5 = 0
>           runspec 10258 [019] 260748.824231: sys_enter: NR 9 (0, c052, 1, 2, 4, 0)
>           runspec 10258 [019] 260748.824245: sys_exit: NR 9 = 140288080809984
>           runspec 10258 [019] 260748.824247: sys_enter: NR 3 (4, c052, 1, 2, 4, 0)
>           runspec 10258 [019] 260748.824249: sys_exit: NR 3 = 0
>
> I guess that the NR # in the end of the line is defined as the systemcall id, but i'm confused about how to match the NR id to the exact systemcall name! Is there any systemcall table or list that I can check the system name accoring to the NR number?

perf-trace uses libaudit to do the conversion. Perhaps something can be 
done for perf-script as well.

David

      reply	other threads:[~2013-04-16 16:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16 15:17 Issue about raw_syscalls! OSDepend
2013-04-16 16:53 ` David Ahern [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=516D81FA.7080302@gmail.com \
    --to=dsahern@gmail.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=osdepend@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).