All of lore.kernel.org
 help / color / mirror / Atom feed
From: song <chensong@kylinos.cn>
To: Jan Kiszka <jan.kiszka@siemens.com>, xenomai@xenomai.org
Subject: Re: some ftrace events are missed
Date: Mon, 10 Feb 2020 20:48:53 +0800	[thread overview]
Message-ID: <d9cae73e-de46-9682-5b2c-c480dc64207f@kylinos.cn> (raw)
In-Reply-To: <9429d894-9879-8266-5c36-7c566de9bf00@siemens.com>

I was pretty sure that all events were enabled before testing with "echo 
1 > events/enable", somehow, the events i cared about were missed.I used 
trace-cmd as your suggestion, it took effect, i saw what i wanted.

I haven't figured out how different they are, but at least i can 
continue my work in my hand, many thanks.

BR

/Song

On 2020/2/3 下午3:00, Jan Kiszka wrote:
> On 02.02.20 13:22, song via Xenomai wrote:
>> hi guys,
>>
>> I'm working on an issue with ftrace events, the call stack is like that:
>>
>> __cobalt_clock_nanosleep
>>      xnthread_suspend
>>          xntimer_start
>>              xnclock_core_ns_to_ticks
>>                  xntimer_enqueue_and_program
>>                      xnclock_program_shot()
>>                          xnclock_core_local_shot
>>                              ipipe_timer_set
>>
>>
>> I tried to enable ftrace event with "-f" in cyclictest,however, i can 
>> only find:
>>
>> cobalt_clock_entry: clock_irq=4
>> cobalt_timer_expire: timer=ffffffc07ffd5800
>> cobalt_clock_exit: clock_irq=4
>> cobalt_timer_start ....
>>
>> event traces like trace_cobalt_clock_nanosleep or 
>> trace_cobalt_thread_suspend are missed, they are all defined in 
>> cobalt_core.h/cobalt_posix.h and visible in 
>> /sys/kernel/debugfs/tracing/events/cobalt-core(cobalt-posix).
>
> Are those events also enabled when you do the tracing? Try catching 
> them via "trace-cmd record -e 'cobalt*' if unsure.
>
> Jan
>
>>
>> Does anyone have the same problem before and i would appreciate it if 
>> you could let me know the way to solve it,many thanks
>>
>> BR
>>
>> Song
>>
>>
>>
>>
>>
>>
>>
>>





      reply	other threads:[~2020-02-10 12:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-02 12:22 some ftrace events are missed song
2020-02-03  7:00 ` Jan Kiszka
2020-02-10 12:48   ` song [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=d9cae73e-de46-9682-5b2c-c480dc64207f@kylinos.cn \
    --to=chensong@kylinos.cn \
    --cc=jan.kiszka@siemens.com \
    --cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.