Skip to contentSkip to conversation

kprobe timestamp

DISCUSSION Yannick Brosseau 3 participants 3 messages Apr 23, 2013 – May 10, 2013 3 messages not in the archive

lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive
Quoted 12 lines · OSDepend

Hi guys,
I just try to use kprobe, and get some thing like below:

java 15893 [015] 96380.588871: timer_cancel: timer=0xffff8804379d6698

            java 15721 [010] 96380.588872: timer_cancel: timer=0xffff8800be3d6698
            java 15893 [015] 96380.588875: timer_expire_entry: timer=0xffff8804379d6698 function=delayed_work_timer_fn now=4391194790
            java 15721 [010] 96380.588876: timer_expire_entry: timer=0xffff8800be3d6698 function=delayed_work_timer_fn now=4391194790

I want to know exactly about the time units of the events, such as 96380.588871, and 96380.588872.
The number befor "." is second or millisecond? and Is the number after "." nanoseconds or microseconds?

What did you use to generate this output? I don't recognize it.

Yannick

_______________________________________________
lttng-dev mailing list
[email protected]
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

#3 lore raw
In reply to a message not in the archive
Quoted 15 lines · OSDepend
Quoted 12 lines

Hi guys,
I just try to use kprobe, and get some thing like below:

java 15893 [015] 96380.588871: timer_cancel: timer=0xffff8804379d6698

            java 15721 [010] 96380.588872: timer_cancel: timer=0xffff8800be3d6698
            java 15893 [015] 96380.588875: timer_expire_entry: timer=0xffff8804379d6698 function=delayed_work_timer_fn now=4391194790
            java 15721 [010] 96380.588876: timer_expire_entry: timer=0xffff8800be3d6698 function=delayed_work_timer_fn now=4391194790

I want to know exactly about the time units of the events, such as 96380.588871, and 96380.588872.
The number befor "." is second or millisecond? and Is the number after "." nanoseconds or microseconds?

Quoted 3 lines
Quoted 3 lines

What did you use to generate this output? I don't recognize it.

Yannick

/usr/src/linux-2.6.38.6/Documentation/trace/kprobetrace.txt
I use kprobe to trace, you can get the documentation of kprobe in the text above. Does any one recognize the time format?

Best,
Chen

#5 lore raw
In reply to a message not in the archive
Quoted 15 lines · * OSDepend ([email protected]) wrote:
Quoted 15 lines · OSDepend
Quoted 12 lines

Hi guys,
I just try to use kprobe, and get some thing like below:

java 15893 [015] 96380.588871: timer_cancel: timer=0xffff8804379d6698

            java 15721 [010] 96380.588872: timer_cancel: timer=0xffff8800be3d6698
            java 15893 [015] 96380.588875: timer_expire_entry: timer=0xffff8804379d6698 function=delayed_work_timer_fn now=4391194790
            java 15721 [010] 96380.588876: timer_expire_entry: timer=0xffff8800be3d6698 function=delayed_work_timer_fn now=4391194790

I want to know exactly about the time units of the events, such as 96380.588871, and 96380.588872.
The number befor "." is second or millisecond? and Is the number after "." nanoseconds or microseconds?

Quoted 7 lines
Quoted 3 lines
Quoted 3 lines

What did you use to generate this output? I don't recognize it.

Yannick

/usr/src/linux-2.6.38.6/Documentation/trace/kprobetrace.txt
I use kprobe to trace, you can get the documentation of kprobe in the text above. Does any one recognize the time format?

I guess you are using ftrace or perf rather than LTTng. You might want to ask them instead.

Thanks,

Mathieu

Signature · 3 lines
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com