On Thu, 2015-02-19 at 17:58 +0000, Pawel Moll wrote: > and what Adrian did, explicitly > defining possible timestamps at perf_event_attr level instead of > relating them to to posix clock ids is the way to go. No strong opinion > here.
One note here: I'd rather make it "processor trace clock", rather than "architecturally defined" one. That way you relate it directly to the time domain and allow userspace decoder to as for it in a architecturally independent way (yes, I'm assuming that there will be only one "type of processor trace in a system :-) Pawel -- 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/
