Hi all,
I have been measuring memory events for the parsec benchmark suite on a dual
socket, quad-core opteron machine with pfmlib version 3.9, kernel pfmon
version 2.82 and kernel version 2.6.29.6 . This is what I use as my
commandline option:
>> pfmon --with-header --outfile=test1 --verbose -u --switch-timeout=100
-eDRAM_ACCESSES_PAGE:HIT,DRAM_ACCESSES_PAGE:MISS,DRAM_ACCESSES_PAGE:CONFLICT,DRAM_ACCESSES_PAGE:ALL
-eDRAM_ACCESSES_PAGE:DCT1_PAGE_HIT,DRAM_ACCESSES_PAGE:DCT1_PAGE_MISS,DRAM_ACCESSES_PAGE:DCT1_PAGE_CONFLICT,DRAM_ACCESSES_PAGE:ALL
$PASEC_COMMAND
The problem is, sometimes, over different runs of the same (multi-threaded)
benchmark, the kernel panics and the machine freezes up. has anybody ever
experienced something of this sort before? Or is there something that I am
doing wrong? Is there a better way to measure these stats (system-wide
monitoring?)?
Any help is appreciated.
Thanks,
Manu
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
perfmon2-devel mailing list
perfmon2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
