Re: Profiling code execution on amd64?

2011-01-17 Thread Fabien Thomas
Last time i've used it it was working but I dont think it is really useful now (from my POV) because you cant have a global view of the system with it and all other reports overlap. With the current state you have: - top mode for fast lookup - text output (replace gprof for me) - kcachegrind

Re: Profiling code execution on amd64?

2011-01-17 Thread Steve Kargl
On Mon, Jan 17, 2011 at 09:45:44AM +0100, Fabien Thomas wrote: Last time i've used it it was working but I dont think it is really useful now (from my POV) because you cant have a global view of the system with it and all other reports overlap. To what does 'it' refer? With the current

Re: Profiling code execution on amd64?

2011-01-15 Thread Hans Ottevanger
On 01/15/11 07:15, Garrett Cooper wrote: On Fri, Jan 14, 2011 at 10:10 PM, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Fri, Jan 14, 2011 at 03:40:46PM -0500, George Neville-Neil wrote: On Jan 13, 2011, at 23:05 , Steve Kargl wrote: On Thu, Jan 13, 2011 at 10:08:30PM -0500, Ryan

Re: Profiling code execution on amd64?

2011-01-14 Thread George Neville-Neil
On Jan 13, 2011, at 23:05 , Steve Kargl wrote: 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

Re: Profiling code execution on amd64?

2011-01-14 Thread Steve Kargl
On Fri, Jan 14, 2011 at 03:40:46PM -0500, George Neville-Neil wrote: On Jan 13, 2011, at 23:05 , Steve Kargl wrote: 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

Re: Profiling code execution on amd64?

2011-01-14 Thread Garrett Cooper
On Fri, Jan 14, 2011 at 10:10 PM, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Fri, Jan 14, 2011 at 03:40:46PM -0500, George Neville-Neil wrote: On Jan 13, 2011, at 23:05 , Steve Kargl wrote: On Thu, Jan 13, 2011 at 10:08:30PM -0500, Ryan Stone wrote: I would suggest using hwpmc

Profiling code execution on amd64?

2011-01-13 Thread Steve Kargl
How does one profile one's code on freebsd-amd64? It seems that gprof is broken. troutmask:kargl[234] time ../penetration CPU time: 7.327 min Start time: 2011-01-13 08:59:18.419 Stop time: 2011-01-13 09:06:39.082 CPU time: 7.34 min 440.68 real 440.25 user 0.11 sys

Re: Profiling code execution on amd64?

2011-01-13 Thread Ryan Stone
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

Re: Profiling code execution on amd64?

2011-01-13 Thread Steve Kargl
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