Date: Thu, 13 Jan 2011 20:05:49 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Ryan Stone <rysto32@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Profiling code execution on amd64? Message-ID: <20110114040549.GA36430@troutmask.apl.washington.edu> In-Reply-To: <AANLkTi=C4L9fn7q8PfJgY=8c24BQnZTC9s7BubsrUYxv@mail.gmail.com> References: <20110113171139.GA32250@troutmask.apl.washington.edu> <AANLkTi=C4L9fn7q8PfJgY=8c24BQnZTC9s7BubsrUYxv@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 13, 2011 at 10:08:30PM -0500, Ryan Stone wrote: > I would suggest using hwpmc for profiling: > > # kldload hwpmc > # pmcstat -S unhalted-cycles -O /tmp/samples.out ../penetration > # pmcstat -R /tmp/samples.out -G /tmp/penetration.txt > > > You can also get pmcstat to generate gprof-compatible output with -g, > but I never use the mode so I'm really not sure what it gives you. I > think that you have to run gprof on the output or something, but don't > hold me to that. Thanks. I'll give it a try, but my initial attempt seems to indicate that one needs to be root to use hwpmc. laptop:kargl[210] pmcstat -S unhalted-cycles -O /tmp/samples.out ../penetration pmcstat: ERROR: Cannot allocate system-mode pmc with specification "unhalted-cycles": Operation not permitted -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110114040549.GA36430>