Yes, ipipe tracing works.
When it is the case, BTW, Here is the result of echoing a new tracer :

$>cat max
I-pipe worst-case tracing service on 2.6.35.11/ipipe-2.12-01
------------------------------
------------------------------
CPU: 0, Begin: 2593605556 cycles, Trace Points: 12 (-10/+5), Length: 268166
us
Calibrated minimum trace-point overhead: 0.023 us

 +----- Hard IRQs ('|': locked)
 |+---- <unused>
 ||+--- <unused>
 |||+-- Xenomai
 ||||+- Linux ('*': domain stalled, '+': current, '#': current+stalled)
 |||||                        +---------- Delay flag ('+': > 1 us, '!': > 10
us)
 |||||                        |        +- NMI noise ('N')
 |||||                        |        |
      Type    User Val.   Time    Delay  Function (Parent)
     #func                   0    0.039  ipipe_check_context+0x8
(tick_nohz_stop_sched_tick+0x31c)
 |   #begin   0x80000001     0    0.051  ipipe_check_context+0xf0
(tick_nohz_stop_sched_tick+0x31c)
 |   #end     0x80000001     0    0.039  ipipe_check_context+0xdc
(tick_nohz_stop_sched_tick+0x31c)
     #func                   0    0.039  __ipipe_unstall_root+0x8
(tick_nohz_stop_sched_tick+0x320)
 |   #begin   0x80000000     0    0.043  __ipipe_unstall_root+0xbc
(tick_nohz_stop_sched_tick+0x320)
 |   #func                   0    0.058  ipipe_check_context+0x8
(__ipipe_unstall_root+0x3c)
 |   +end     0x80000000     0    0.046  __ipipe_unstall_root+0xa8
(tick_nohz_stop_sched_tick+0x320)
     +func                   0    0.041  ipipe_suspend_domain+0x8
(cpu_idle+0xb0)
 |   +begin   0x80000001     0    0.060  ipipe_suspend_domain+0x1e0
(cpu_idle+0xb0)
 |   +end     0x80000001     0    0.043  ipipe_suspend_domain+0x220
(cpu_idle+0xb0)
>|   +begin   0x80000000     0! 2146.524  cpu_idle+0xe8 (rest_init+0x94)
:|   +func               268166    0.045  __ipipe_grab_timer+0x8
(__ipipe_ret_from_except+0x0)
:|   +begin   0x00000200 268166    0.046  __ipipe_grab_timer+0x84
(__ipipe_ret_from_except+0x0)
:|   +func               268166    0.060  __ipipe_dispatch_wired_nocheck+0x8
(__ipipe_grab_timer+0x138)
:|  # func               268166    0.054  xnintr_clock_handler+0x8
(__ipipe_dispatch_wired_nocheck+0x104)
:|  # func               268166    0.050  xntimer_tick_aperiodic+0x8
(xnintr_clock_handler+0xd0)
:|  # func               268166    0.060  xntimer_next_local_shot+0x8
(xntimer_tick_aperiodic+0x304)
:|  # func               268166    0.049  xnintr_host_tick+0x8
(xnintr_clock_handler+0x1f4)
:|  # func               268166    0.085  __ipipe_set_irq_pending+0x8
(xnintr_host_tick+0x94)
:|   +func               268166    0.065  __ipipe_walk_pipeline+0x8
(__ipipe_dispatch_wired_nocheck+0x148)
:|   +func               268166    0.061  __ipipe_sync_stage+0x8
(__ipipe_walk_pipeline+0x1a8)
<|   #end     0x80000000 268166    0.042  __ipipe_sync_stage+0x238
(__ipipe_walk_pipeline+0x1a8)
     #func               268166    0.042  irq_enter+0x8
(__ipipe_sync_stage+0x260)
     #func               268166    0.046  rcu_irq_enter+0x8 (irq_enter+0x38)
     #func               268167    0.043  idle_cpu+0x8 (irq_enter+0x44)
     #func               268167    0.039  ipipe_check_context+0x8
(irq_enter+0x84)
 |   #begin   0x80000001 268167    0.000  ipipe_check_context+0xf0
(irq_enter+0x84)


$>echo function_graph > current_tracer
[  275.698664] ------------[ cut here ]------------
[  275.755250] ------------[ cut here ]------------
[  275.810547] Kernel stack overflow in process dc6bf020, r1=dc838250
[  275.896276] Kernel panic - not syncing: kernel stack overflow
[  275.965200] Rebooting in 30 seconds..

2011/9/23 Gilles Chanteperdrix <gilles.chanteperd...@xenomai.org>

> On 09/23/2011 09:58 AM, Jean-Michel Hautbois wrote:
> > Hi List,
> >
> > I am trying to use ftrace on a P2020 board, using the following :
> > - Linux 2.6.35-11
> > - Xenomai 2.5.5.1 (or 2.5.6, same problem)
> > - ipipe 2.12-01
> >
> > I launch it using :
> > $> mkdir /tmp/debug
> > $> mount -t debugfs nodev /tmp/debug
> > $> cd /tmp/debug/tracing
> > $> echo function_graph > current_tracer
> >
> > The last one fails (it hangs the CPU, I cannot do anything than hard
> reset).
> > Do you know what could cause that ?
> > As I can't have any trace, I don't really know how to go further, and
> before
> > using a BDI I would like to know if it is a known issue, as I could not
> find
> > anything related to this in the recent changes...
> >
> > Thanks in advance for your help,
> > Regards,
> > JM
>
> Does the I-pipe tracer work?
> See:
> http://www.xenomai.org/index.php/I-pipe:Tracer
>
>
> --
>                                            Gilles.
>
_______________________________________________
Xenomai-core mailing list
Xenomai-core@gna.org
https://mail.gna.org/listinfo/xenomai-core

Reply via email to