Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] Getting current process from Log files
Date: Fri, 1 Apr 2011 11:18:14 -0400	[thread overview]
Message-ID: <BLU0-SMTP51624D82F08D1B799D398596BE0@phx.gbl> (raw)
In-Reply-To: <AANLkTikuECjnSYBuD+US_eBknyEcG6jR2rPZsGfSdo2w@mail.gmail.com>

* Radhika Chowdary (radhika.putty at gmail.com) wrote:
> Hi
> 
> We are implementing importer for LTTng and not using any existing C parser
> or linuxtools plugins.

Why ? You might want to consider looking at libltttraceread and lttv.
These problems have already been solved, and the code is public.

> I need some info on how we get the currently running
> process. From what i see from the existing C parser code i understand its
> the sched_schedule event which can help in getting currently running
> process. We get the timestamp of when a sched change event happened and add
> the process to the stack with timestamp. So any event occuring after the
> sched_schedule event we get the process that was scheduled in as currently
> running process.

.. for the cpu sched_schedule was executed on.

> Is my understanding currect. If that is true and we get an
> event before any sched_schedule or fork events how can we get the process
> that generated the event. Would it be the init process?

Nope. See state.c in lttv. This is why we have unknown state at trace
start, ability to build the state from the events incrementally for
flight recorder mode, and "state dump" machinery to get to a point where
the state is fully known when we have a "normal/discard" trace.

Thanks,

Mathieu

> 
> Thanks
> Radhika

> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev


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




      parent reply	other threads:[~2011-04-01 15:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01  7:54 Radhika Chowdary
2011-04-01  7:54 ` Radhika Chowdary
2011-04-01  7:54 ` Radhika Chowdary
2011-04-01 15:18 ` Mathieu Desnoyers [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=BLU0-SMTP51624D82F08D1B799D398596BE0@phx.gbl \
    --to=compudj@krystal.dyndns.org \
    /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