[ltt-dev] Getting current process from Log files

[ltt-dev] Getting current process from Log files

[Radhika Chowdary]

Hi

We are implementing importer for LTTng and not using any existing C parser
or linuxtools plugins. 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. 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?

Thanks
Radhika
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/ltt-dev/attachments/20110401/ba75e611/attachment.htm>

[ltt-dev] Getting current process from Log files

[Radhika Chowdary]

Hi

We are implementing importer for LTTng and not using any existing C parser
or linuxtools plugins. 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. 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?

Thanks
Radhika
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20110401/ba75e611/attachment-0002.htm>

[ltt-dev] Getting current process from Log files

[Radhika Chowdary]

Hi

We are implementing importer for LTTng and not using any existing C parser
or linuxtools plugins. 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. 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?

Thanks
Radhika
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20110401/ba75e611/attachment-0003.htm>

[ltt-dev] Getting current process from Log files

[Mathieu Desnoyers]

* 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