From: <rk...@nc...> - 2004-07-05 15:48:14
|
Kursad, Thanks for the update on how things are going. It sounds like you're making some progress, I hope the comments were helpful. I'd like to make sure I'm understanding your experience because as you know, PerfSuite is still in a beta release. It would be nice to adjust things/problems before going final later this year. So to recap: you are saying that PIII configs that do not include derived events work for you, is that right? It seems to me that if counter resources are not available, that psrun shouldn't even write out an XML document, but instead report an error. Does that seem like more reasonable behavior? P4 - same thing? If you could send me an example config that shows this behavior, it would help me test/verify here on our systems. The Perl script idea sounds good: there's no Perl anything currently in the PerfSuite distribution but if you develop a post-processor that might be interesting to others, I'd love to hear of it. Also - if you're finding there are particular metrics you're using frequently, you may be able to add them to the default calculations that psprocess does by adding them into its "database". That's an XML document that gets installed here: $PREFIX/share/perfsuite/xml/pshpwc/PAPI_metrics.xml Thanks again for the update, Rick > Hi Rick, > > Looks like this was an issue that you were aware of. When I don't pass any > XML configuration file to psrun, it works perfectly. Turns out that the PAPI > 3 standard config file for Pentium 3 (P6) includes some comments from you on > why no derived events are included in the XML file. This config file works > for us, we will just have to derive the derived events ourselves by writing > a Perl script. > > What I tried to do was write my own config file that included all standard > and derived metrics. PAPI 3 still fails and gives me all zeros if I use such > a file. > > Regards, |