> 2.6.38 on imx51 babbage board.
Then I won't be able to provide you with a simple hack, sorry...
Generally looks like the sched_clock implementation is missing so the
ftrace is reverting to jiffies as the timestamp source (this was the
case with mach-vexpress with kernels < 2.6.37)
Good luck!
On Mon, Feb 21, 2011 at 6:31 PM, Pawel Moll wrote:
> Hello,
>
> > When I am trying to use ftrace to measure cpuidle latency, I find that
> > the timestamp is always ending with , like below.
> > -0 [000]79.53: cpu_idle: state=0 cpu_id=0
>
> What platform and kernel is it
Hello,
> When I am trying to use ftrace to measure cpuidle latency, I find that
> the timestamp is always ending with , like below.
> -0 [000]79.53: cpu_idle: state=0 cpu_id=0
What platform and kernel is it? 2.6.35 and Versatile Express by any
chance?
Cheers!
Paweł
Hi there,
When I am trying to use ftrace to measure cpuidle latency, I find that the
timestamp is always ending with , like below.
bash-2.05b# head trace
# tracer: nop
#
# TASK-PIDCPU#TIMESTAMP FUNCTION
# | | | | |
-0 [
