Date: Sun, 23 Nov 2008 20:56:03 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: Attilio Rao <attilio@freebsd.org> Cc: FreeBSD Arch <arch@freebsd.org>, freebsd-performance@freebsd.org, Joseph Koshy <jkoshy@freebsd.org> Subject: Re: [PATCH] pmcannotate tool Message-ID: <20081123205603.17752y578er4bcqo@webmail.leidinger.net> In-Reply-To: <3bbf2fe10811230502t3cc52809i6ac91082f780b730@mail.gmail.com> References: <3bbf2fe10811230502t3cc52809i6ac91082f780b730@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Attilio Rao <attilio@freebsd.org> (from Sun, 23 Nov 2008 14:02:22 +0100): > pmcannotate is a tool that prints out sources of a tool (in C or > assembly) with inlined profiling informations retrieved by a prior > pmcstat analysis. > If compared with things like callgraph generation, it prints out > profiling on a per-instance basis and this can be useful to find, for > example, badly handled caches, too high latency instructions, etc. Can this also be used to do some code coverage analysis? What I'm interested in is to enable something, run some tests in userland, disable this something, and then run a tool which tells me which parts of specific functions where run or not. At first I hoped I can use dtrace for this... I had a dtrace training and seen the userland probes in action, where you can trace every ASM instruction, but unfortunately you can not do this with kernel probes. I tried with fbt and syscall on a Solaris 10 machine. I haven't tested with FreeBSD-dtrace yet, but I doubt it is more advanced in this regard than the Solaris dtrace. So I'm still searching. Bye, Alexander. -- We should keep the Panama Canal. After all, we stole it fair and square. -- S. I. Hayakawa http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081123205603.17752y578er4bcqo>