(a) Does your program run under collect without specifying the hardware
counter events.
(b) What lock is your program stuck on? Try plockstat. It looks like
your code spends 50% of its time in locks anyway.
Regards,
Darryl.
On 08/27/10 01:44, Kishore Kumar Pusukuri wrote:
Hi,
I am trying to play with the utility "collect" for studing TLB misses of a multi-threaded program running on my AMD multi-core machine equipped with OpenSolaris.2009.06. However, the program is hanging (with and also without umask) on when I used collect utility. Please find the "prstat -m" output of the program with and without collect utlity. Is this problem with the collect utility or the way I used it? Please let me know.
$ collect -h DC_dtlb_L1_miss_L2_miss~umask=0x01 ./program
$ uname -a
SunOS opensolaris 5.11 snv_111b i86pc i386 i86pc Solaris
prstat output with collect
==========================
PID USERNAME USR SYS TRP TFL DFL LCK SLP LAT VCX ICX SCL SIG PROCESS/NLWP
2201 pusukuri 0.0 0.0 0.0 0.0 0.0 100 0.0 0.0 0 0 0 0 program/16
prstat output without collect
=============================
PID USERNAME USR SYS TRP TFL DFL LCK SLP LAT VCX ICX SCL SIG PROCESS/NLWP
2311 pusukuri 51 0.5 0.0 0.0 0.0 48 0.0 0.2 1K 23 2K 0 program/16
--
Darryl Gove
Compiler Performance Engineering
Blog : http://blogs.sun.com/d/
Books: http://my.safaribooksonline.com/9780321711441
http://my.safaribooksonline.com/9780768681390
http://my.safaribooksonline.com/0595352510
_______________________________________________
perf-discuss mailing list
perf-discuss@opensolaris.org
