Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: syed.shariyar@gmail.com (Shariyar)
Subject: [lttng-dev] Extracting System Call IDs By Using TMF
Date: Sat, 30 Nov 2013 20:23:58 -0500	[thread overview]
Message-ID: <CAKQh6phjqskTkP5OfG3-NN9UBhWxK6UtiyZA+YcoG=x7aYS=yg@mail.gmail.com> (raw)

Hi Matthew:

In that case I need to create a map myself.

I  was looking for the system call ids for the following reasons:

1. In LTTng 1.0, there were several occasions when only the system call id
was found in a trace but not the names. If such is the case with LTTng 2.0,
then my concern is  that it would be better to extract ids.

2. Trained models need to be stored in database and ids will take lesser
sapce as the model grows with time.

Regards,
Shariyar



Message: 1
Date: Fri, 29 Nov 2013 10:39:54 -0500
From: Matthew Khouzam <matthew.khouzam@ericsson.com>
To: <lttng-dev at lists.lttng.org>
Subject: Re: [lttng-dev] Extracting System Call IDs By Using TMF
Message-ID: <5298B54A.5080907 at ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"

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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20131130/5e8eb168/attachment-0001.html>


             reply	other threads:[~2013-12-01  1:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-01  1:23 Shariyar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-11-29  0:29 Shariyar
2013-11-29 15:39 ` Matthew Khouzam
2013-11-29 16:59   ` Francis Giraldeau

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='CAKQh6phjqskTkP5OfG3-NN9UBhWxK6UtiyZA+YcoG=x7aYS=yg@mail.gmail.com' \
    --to=syed.shariyar@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