* Guillaume Chazarain <guichaz@xxxxxxxx> wrote: > > Correction: it was not a high res time source, it was "the > > scheduler's per-cpu, non-exported, non-coherent, > > warps-and-jumps-like-hell high-res timesource that was intentionally > > called the _sched_ clock" ;-) > > I think the warts of cpu_clock() are fixable, except maybe > unsynchronization on SMP which is harder. yes - but in terms of v2.6.24, the bkltrace patch i sent is a lot less risky. Ingo - To unsubscribe from this list: send the line "unsubscribe linux-btrace" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
