> That's wrong. It does not respect perf_event_attr::clock_id. Ok.
Are we really defaulting to real time now? (CLOCK_REALTIME == 0) What happens when ntpd is active and lets the time drift? That sounds very bad for event accuracy. The clockid patch looks broken to me. At least it should default to MONOTONIC time, not just the time that happens to be 0 by accident. Also I question we really need that many different kinds of time stamps. -Andi -- a...@linux.intel.com -- Speaking for myself only. -- 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/