|Re: [tracecompass-dev] ftrace & xenomai|
I am on vacation this week and next.
Fabien, could you describe what a scheduler switch event looks like?
In trace compass, right click on an event in the events list and select copy to clipboard, pasting the result should look like this
Timestamp Channel CPU Event type Contents TID Prio PIDor
16:13:13.326 391 792 ss_2 2 sched_switch prev_comm=swapper/2, prev_tid=0, prev_prio=20, prev_state=0, next_comm=Xorg, next_tid=976, next_prio=20, context._tid=0, context._pid=0 0 20
Timestamp CPU Event type Contents PID
00:36:01.624 114 000 2 sched_switch prev_pid=12958, prev_prio=120, next_pid=8, name=sched_switch, prev_comm=sh, prev_state=1, next_comm=rcu_preempt, ts=365761624114000, next_prio=120 12958
pretty similar 😊
if the xenomai tracepoint is similar, we can get it to work pretty easily.
From: tracecompass-dev-bounces@xxxxxxxxxxx <tracecompass-dev-bounces@xxxxxxxxxxx> on behalf of Michel Dagenais <michel.dagenais@xxxxxxxxxx>
Sent: Tuesday, August 14, 2018 11:56:12 AM
To: tracecompass developer discussions
Subject: Re: [tracecompass-dev] ftrace & xenomai
Geneviève is away as well.
Indeed, the Control Flow View is based on the state of threads. When the trace is read, specific events (Linux scheduling events) are recognized as changing the state of the threads. This is achieved in the "state provider" which can be defined either with Java code or with a declarative XML file.
You need to define how the related Xenomai events change the threads state. You also ideally need to insure that Xenomai threads creation and deletion are handled properly.
This is described in the Data Driven Analysis section of the manual, (defining XML components, defining an XML state provider...).
Back to the top