On Wed, 4 Sep 2013, Michael Kerrisk (man-pages) wrote: > > I don't know. But looking at the git repo, it seems in the first git commit > > (1da177e4c3f41524e886b7f1b8a0c1fc7321cac2) it was already safe, What do you mean by "safe"? Note that the manpage was written mainly based on my experience on IA64 with ITC registers. There were numerous bugs in 2004/2005 due to glibc / kernel / firmware issues. > So, some history: CLOCK_THREAD_CPUTIME_ID and CLOCK_PROCESS_CPUTIME_ID > first appeared in 2.6.12, as far as I know. Those were earlier supported by glibc before kernel support was added. At some point they were used in some weird scheme to retrieve TSC/ITC register contents. > point, but it's unclear to me when that point could have been, since > the timelines don't seem to match up (unless, of course, your > suppositions are wrong, Rodrigo, but I'm not assuming that at this > point). Only have a vague recollection of these things at this point and I have no longer access to my email from that time period since I am no longer with SGI. -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html