On Mon, May 04, 2015 at 01:05:19PM -0700, Drew Richardson wrote: > I'm collecting and merging data from perf, with Android Atrace data > (writes to /sys/kernel/debug/tracing/trace_marker) which ends up in > the ftrace stream and other measurements collected from > userspace. Currently the only clock readable from userspace, supported > by perf and by ftrace is CLOCK_MONOTONIC. However this clock is > affected by the incremental adjustments performed by adjtime(3) and > NTP.
Which should not matter at all, right? If both sources are using the same clock (they are) then its trivial to merge them and everything works as expected. > But I'd prefer to use a clock that is advancing at a consistent > rate, hence CLOCK_MONOTONIC_RAW. Right, Mathieu is asking _why_ you prefer that? -- 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/
