Date: Wed, 22 Mar 2006 00:10:09 +0530 From: "Joseph Koshy" <joseph.koshy@gmail.com> To: "Andrew Gallatin" <gallatin@cs.duke.edu> Cc: Robert Watson <rwatson@freebsd.org>, current@freebsd.org Subject: Re: The sixty second pmc howto Message-ID: <84dead720603211040h3db11614v31ae5d7d9a0c1a28@mail.gmail.com> In-Reply-To: <17440.17965.497455.777452@grasshopper.cs.duke.edu> References: <20060223143856.O9642@fledge.watson.org> <17405.53911.686306.362353@grasshopper.cs.duke.edu> <84dead720603202346t6fe1e94cve033bf002dffa90a@mail.gmail.com> <17440.17965.497455.777452@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> For a few modules, I suppose it is OK. But it makes it hard to > see the "big picture" when a number of modules are loaded. > Is there any chance you have enough information to hack > together a view similar to oprofile's opreport -l? Or > (even better) opreport -ld Can you post what that looks like? There is a lot of information in hwpmc's event log, but gprof(1) is only able to deal with one (object) file at a time. This restriction is likely to pinch even more when callgraphs are implemented. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?84dead720603211040h3db11614v31ae5d7d9a0c1a28>