Messages in this thread | | | Date | Wed, 30 May 2007 15:49:07 +0200 | From | Ingo Molnar <> | Subject | Re: [PATCH 3/5] lockstat: core infrastructure |
| |
* Steven Rostedt <rostedt@goodmis.org> wrote:
> [...] We can argue that sched_clock is "good enough". If someone > wants better accounting of locks on some other arch, they can simply > change sched_clock to be more precise.
exactly. Imprecise sched_clock() if there's a better fast clock source available is a bug in the architecture code. If the only available clocksource is 1 msec resolution then there's no solution and nothing to talk about - lock statistics will be 1msec granular just as much as scheduling.
Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |