From: Rick K. <rk...@nc...> - 2006-11-20 13:39:55
|
Niall, >> Thanks for getting back to me. I have checked the list of supported >> events from psinv -p against the events listed in the papi3_k8.xml configuration file >> and all the events in the config file are supported. I also ran psrun -i >> to ensure that it is using the papi3_k8.xml config file. Attached is the >> output of psinv -p and also the the config file papi3_k8.xml. > > I removed all events from the papi3_k8.xml config file and started > adding them back in one by one. Everything works fine with all be > events except for PAPI_L1_TCM and PAPI_L2_TCA even though both these > events appear in the psinv -p output. Sounds like some good detective work on your end, thanks for checking into things and reporting. Now, as to why this is going on I have to admit being stumped at the moment. This would seem at first glance to be something going wrong in either the PAPI or perfctr layers. Within the PAPI 3.2.1 distribution there is a utility called "papi_avail" that can print out information about mappings of PAPI events to the native counters that may provide a clue. It's invoked as "papi_avail -e EVENTNAME" where EVENTNAME is the name of the PAPI event one wants more information about. You might try that utility with the events above and see what the output is to get started. Unfortunately, I do not have access to an Opteron with the kernel support required to test this out, but if this limitation is a problem for you we can try to look further into it. Rick p.s. for detailed debugging information, PerfSuite's configure script supports an option --enable-debug and the software recognizes an environment variable PS_DEBUG which if set to 3 or higher will dump a lot of information about what's going on underneath to help locate sources of errors. |