Ingo Molnar <[EMAIL PROTECTED]> 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. -- Guillaume -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
