Date: Mon, 24 Nov 2008 00:46:29 +0100 From: "Attilio Rao" <attilio@freebsd.org> To: "Alexander Leidinger" <Alexander@leidinger.net> Cc: FreeBSD Arch <arch@freebsd.org>, freebsd-performance@freebsd.org, Joseph Koshy <jkoshy@freebsd.org> Subject: Re: [PATCH] pmcannotate tool Message-ID: <3bbf2fe10811231546r44bd2aafqa3d714a4955f52ad@mail.gmail.com> In-Reply-To: <20081123205603.17752y578er4bcqo@webmail.leidinger.net> References: <3bbf2fe10811230502t3cc52809i6ac91082f780b730@mail.gmail.com> <20081123205603.17752y578er4bcqo@webmail.leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
2008/11/23, Alexander Leidinger <Alexander@leidinger.net>: > 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. Yes, this is exactly what it does. You can see traces for any sampled PC and so get a profiling anslysis on a per-instance basis. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3bbf2fe10811231546r44bd2aafqa3d714a4955f52ad>