From: matthew.khouzam@ericsson.com (Matthew Khouzam)
Subject: [lttng-dev] Extracting System Call IDs By Using TMF
Date: Fri, 29 Nov 2013 10:39:54 -0500 [thread overview]
Message-ID: <5298B54A.5080907@ericsson.com> (raw)
In-Reply-To: <CAKQh6pji+x7NV4nURCeyozMZkbJJXfAbHvLNJJ95y21CoXT-=Q@mail.gmail.com>
Hi Shariyar,
I would like to know what is the need for the syscall id? I looked at
kernel events, and they store the system call name, not the id? Is it
for performance reasons, or is there some functionality that can be
achieved from a call ID that cannot from a name?
On 13-11-28 07:29 PM, Shariyar wrote:
>
> I need information on how to extract system call ids from a kernel
> level trace by using TMF.
> For example, a sample code to iterate through a kernel trace in CTF
> format is given below.
>
> In this code, I am able to extract the system call name and its return
> value. However, from the *event.getContent()* function, I could not
> get the system call id for the corresponding system call name.
>
> Kindly let me know, how to extract the system call id? By system call
> id I mean the actual system call id assigned by Linux to a system call
> as shown on this site: http://syscalls.kernelgrok.com/
>
next prev parent reply other threads:[~2013-11-29 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 0:29 Shariyar
2013-11-29 15:39 ` Matthew Khouzam [this message]
2013-11-29 16:59 ` Francis Giraldeau
2013-12-01 1:23 Shariyar
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=5298B54A.5080907@ericsson.com \
--to=matthew.khouzam@ericsson.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