|> mcount() generates the call graph; I am talking about the statistical
|> sampling provided by the profiling timer. I understand why system
|> calls are not sampled, but I am not sure I like it. High-latency
|> system calls can have a big effect on an application's performance.
|> If your application is slow because it makes too many slow system
|> calls, there does not seem to be any easy way to find that out; the
|> results of gprof can even be misleading.
gprof is not for profiling the kernel. Only user time is counted.
Andreas.
-- Andreas Schwab "And now for something SuSE Labs completely different." schwab@suse.de SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/