> Anyway, attached patch is capable of displaying milliseconds approximation > for each instruction.
You realize that the events perf is not counting do not directly map to wall time? Even if you count cycles, the cycles are either stopping in idle or changing unit as the CPU's frequencies change. For other events the relationship is even more remote, think what happens when counting cache or TLB misses. Also even if it was mapping to time somehow, it's just a hit, not a duration, so it cannot say how long a individual instruction took. So you cannot map a sample event to time. To do what you want you would need to use something like processor trace, which can do exact accounting. I think the only thing that makes sense is to account it relative to the event counts. -Andi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
