On Wed, 11 Dec 2013 18:06:06 -0800 Sonny Rao <sonny...@chromium.org> wrote:
> > ftrace has several clocks that it uses: > > > > o local - basically sched_clock() > > o global - something like hpet that is monotonic across CPUs but slower > > o counter - a simple atomic counter (no time associated to it) > > o uptime - jiffy counter > > o perf - trace_clock, which is what perf uses > > o x86_tsc - the raw tsc counter. > > > > # cat /sys/kernel/debug/trace_clock > > [local] global counter uptime perf x86-tsc > > > > Ah ok sorry for the incorrect info there, thanks for clarifying. > So, If I wanted to make sure everything is synced up between ftrace > events and perf events I should say perf here instead of local. Correct, that's why I created that clock. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
