Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1534842
| From | Will Deacon <will.deacon@arm.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] trace: extend trace_clock to support arch_arm clock counter |
| Date | 2016-12-02 12:10 +0100 |
| Message-ID | <sJTT3-34R-5@gated-at.bofh.it> (permalink) |
| References | <sJRex-16S-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, Dec 02, 2016 at 01:44:55PM +0530, Srinivas Ramana wrote: > Extend the trace_clock to support the arch timer cycle > counter so that we can get the monotonic cycle count > in the traces. This will help in correlating the traces with the > timestamps/events in other subsystems in the soc which share > this common counter for driving their timers. I'm not sure I follow this reasoning. What's wrong with nanoseconds? In particular, the "perf" trace_clock hangs off sched_clock, which should be backed by the architected counter anyway. What does the cycle counter in isolation tell you, given that the frequency isn't architected? I think I'm missing something here. Will
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH] trace: extend trace_clock to support arch_arm clock counter Srinivas Ramana <sramana@codeaurora.org> - 2016-12-02 09:20 +0100
Re: [PATCH] trace: extend trace_clock to support arch_arm clock counter Will Deacon <will.deacon@arm.com> - 2016-12-02 12:10 +0100
Re: [PATCH] trace: extend trace_clock to support arch_arm clock counter Srinivas Ramana <sramana@codeaurora.org> - 2016-12-04 09:40 +0100
Re: [PATCH] trace: extend trace_clock to support arch_arm clock counter Will Deacon <will.deacon@arm.com> - 2016-12-06 13:30 +0100
csiph-web