Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > I mean, the darned thing is called from sched_clock(), which can be > concurrently called on separate CPUs and which can be called from > interrupt context (with an arbitrary nesting level!) while it was running > in process context. > > Who let that thing into Linux? Having crawled all over it, and argued with Nicolas and Panasonic about it, I think it's safe in sched_clock(), provided sched_clock() never gets preempted - which appears to be the case. David -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html