Re: [PerfSuite-bugs] [PerfSuite 0.6.2a5] testsuite: 1 2 3 4 5 8 11 12 15 16 19 20 22 23 26 27 28 29 failed

[Rick K. <rk...@nc...>]

Berkin,

On Fri, 25 Aug 2006, Berkin Ozisikyilmaz wrote:

> Sorry for my late reply, I have been out of town for the last 2 weeks.

Not to worry.  It's summer and we are all in and out of town :)

> I have used psprocess with the -e option, but still I can't get counter
> values like branch instructions, conditional branch instructions
> mispredictied, total translation lookaside buffer misses, level 1
> instruction cache misses etc. Is there a special flag that I need to use
> while using psrun command?
>

It's still rather hard for me to see what the problem is or to diagnose, 
but I will tell you that based on the XML output you sent earlier in 
August, you had selected profiling using the "profil.xml" configuration 
file that's included in PerfSuite.

That particular configuration does profiling based on the library routine 
profil(), which is a purely time-based profile, similar to what gprof 
uses.   It will not profile based on hardware events such as you list but 
will only display time spent in the various portions of your program.

To profile based on hardware events, you should select a different type of 
configuration file.  Once you've installed PerfSuite, there will be a 
variety of example configurations installed in the directory:

$PREFIX/share/perfsuite/xml/pshwpc

You might want to take a look through these files (only concern yourself 
with the ones with a .xml extension) to see what they do.  You can then 
use one of them, tailored as you like, by either:

1. setting the environment variable PS_HWPC_CONFIG to the pathname of the 
configuration file you've selected before running psrun on your 
executable, or

2. supplying the option "-c FILENAME" to psrun, where FILENAME is again 
the full path to the configuration file you want to use.

Once you've run your program this way and obtained an XML output document, 
then use:

psprocess -e YOURPROGRAM XML-OUTPUT-DOCUMENT

to view the results.

Please note that the current release of PerfSuite only allows profiling on 
one event per run.

Hope this helps clarify operation,

Rick