On Wed, 2015-01-21 at 17:44 +0000, John Stultz wrote: > That said, there is the dynamic posix clockids. I'm not sure if it > would make sense, but even if we don't bump MAX_CLOCKS, might there > be some case where someone wants to use a dynamic posix clock for the > perf reference? If I remember correctly, last time I tried to use dynamic posix clocks in the perf context, one needed to open a ptp character device in order to get a file descriptor, than translated into a clockid_t value - correct me if I'm wrong. But here you get the fd from the sys_perf_open() and clock_*() doesn't know anything about such descriptor. I was looking into a way of associating a random clock with a random fd, so that perf could "attach" itself to the clock API at will, but it turned out not to be trivial (I'd have to dig through old threads to remember all the nasty details). The good thing is that it looks like the immediate need for this was no more, with perf using monotonic clock as the clock source. It will come back when we get into hardware trace correlation, but one step at a time... Pawel -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
