You can subscribe to this list here.
2004 |
Jan
|
Feb
(2) |
Mar
(2) |
Apr
|
May
|
Jun
(1) |
Jul
(6) |
Aug
(3) |
Sep
|
Oct
(1) |
Nov
|
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
(6) |
May
|
Jun
(4) |
Jul
(3) |
Aug
|
Sep
|
Oct
(2) |
Nov
(12) |
Dec
(10) |
2006 |
Jan
(27) |
Feb
(4) |
Mar
(3) |
Apr
(5) |
May
(5) |
Jun
(1) |
Jul
(2) |
Aug
|
Sep
(7) |
Oct
(5) |
Nov
(11) |
Dec
(5) |
2007 |
Jan
(15) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
2008 |
Jan
(7) |
Feb
(9) |
Mar
(2) |
Apr
(1) |
May
|
Jun
(6) |
Jul
(2) |
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
(1) |
2009 |
Jan
(11) |
Feb
|
Mar
(2) |
Apr
(1) |
May
(8) |
Jun
(11) |
Jul
(9) |
Aug
(12) |
Sep
(1) |
Oct
(3) |
Nov
(10) |
Dec
|
2010 |
Jan
(3) |
Feb
(1) |
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
2011 |
Jan
(2) |
Feb
(2) |
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
(1) |
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
From: Rick K. <rk...@nc...> - 2006-12-19 13:08:00
|
Chunhua, Most of the command-line options that psrun accepts have an equivalent environment variable that can be used to cause the same behavior when using the libpshwpc API. In the case of the "-c" option, the environment variable is PS_HWPC_CONFIG, which would be set to the same value that would otherwise be given to psrun. The psrun man page or the output of "psrun -h" are the best places to check for option and environment settings. For your example below, either: env PS_HWPC_CONFIG=aaa.xml ./matvec-r4-ps PS_HWPC_CONFIG=aaa.xml ./matvec-r4-ps should do the trick, depending on whether you're using csh or sh. Rick On Mon, 18 Dec 2006, Chunhua Liao wrote: > Hi, > I was playing with the example program matvec from > /usr/apps/tools/perfsuite/share/perfsuite/examples on cobalt. It > seemed that the executable matvec-r4-ps from matvec-ps.f could > generate perfsuite's .xml result without invoking 'psrun' since it > uses the libpshwpc library directly. > > My question is: how to specify a customized configuration xml when > running matvec-r4-ps, similar to using 'psrun -c' ? I tried to type' > matvec-r4-ps -c aaa.xml' but no luck. > > Thanks for your attention. > > Chunhua Liao > > |
From: Rick K. <rk...@nc...> - 2006-12-11 16:18:05
|
PerfSuite 0.6.2 alpha 6 is now available. This release includes the following updates: - Changes to provide compatibility with PAPI 3.5.0 - Support for adjustable multiplexing intervals (requires PAPI 3.5.0) - New capability for MD5 checksum generation, stored in output XML documents along with performance data There are also additional bug fixes and enhancements in this release; please see the CHANGES file for a complete listing. URL: http://perfsuite.sourceforge.net/ Rick |
From: Rick K. <rk...@nc...> - 2006-12-08 16:17:54
|
Niall, Following up on this from last month: I am in the final stages of preparing a new release of PerfSuite and am wondering if you were able to clarify the conflicts reported below? To be on the safe side, I could remove both PAPI_L1_TCM and PAPI_L2_TCA from the default K8 configuration XML document, but thought I might check with you first just in case.... Thanks, Rick On Mon, 20 Nov 2006, Niall Moran wrote: >>> 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. >> >> 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. > > Running papi_avail for both these events works fine and says that they > pass. I then tried adding both these events and these alone to the > config file and it worked fine. It appears that there are > conflicts between these events and some of the others. I ran into a > similar problem using papi with itc on an itanium2. I will recompile > perfsuite with the debugging enabled and will experiment with different > configs to try to get an idea of which events are conflicting with which. > > Niall. > |
From: Rick K. <rk...@nc...> - 2006-12-02 00:21:21
|
A user reported via perfsuite-bugs that problems were encountered when running PerfSuite's test suite after building with the new PAPI 3.5.0 release. The problem manifested itself when profiling with PAPI, specifically after the measurement had completed and PerfSuite attempts to clean up its PAPI data structures. I've tracked down this problem and determined that it's in the way PerfSuite was using PAPI - the use didn't cause errors in prior releases of PAPI but does with PAPI 3.5.0 (i.e. it is/was a bug in PerfSuite). A fix has also been developed that will appear in the next PerfSuite release, but I'm sending this notice to the users mailing list in case anyone encounters the same problem after having upgraded their copy of PAPI. Runs in counting mode should be fine with PAPI 3.5.0, but not profiling. Rick |
From: Niall M. <nia...@ic...> - 2006-11-20 15:12:14
|
> >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. >=20 > Sounds like some good detective work on your end, thanks for checking int= o=20 > things and reporting. Now, as to why this is going on I have to admit=20 > being stumped at the moment. This would seem at first glance to be=20 > something going wrong in either the PAPI or perfctr layers. Within the= =20 > PAPI 3.2.1 distribution there is a utility called "papi_avail" that can= =20 > print out information about mappings of PAPI events to the native counter= s=20 > that may provide a clue. It's invoked as "papi_avail -e EVENTNAME" where= =20 > EVENTNAME is the name of the PAPI event one wants more information about.= =20 > You might try that utility with the events above and see what the output= =20 > is to get started. Unfortunately, I do not have access to an Opteron wit= h=20 > the kernel support required to test this out, but if this limitation is a= =20 > problem for you we can try to look further into it. >=20 > p.s. for detailed debugging information, PerfSuite's configure script=20 > supports an option --enable-debug and the software recognizes an=20 > environment variable PS_DEBUG which if set to 3 or higher will dump a lot= =20 > of information about what's going on underneath to help locate sources of= =20 > errors. Running papi_avail for both these events works fine and says that they pass. I then tried adding both these events and these alone to the config file and it worked fine. It appears that there are conflicts between these events and some of the others. I ran into a similar problem using papi with itc on an itanium2. I will recompile perfsuite with the debugging enabled and will experiment with different configs to try to get an idea of which events are conflicting with which.= =20 Niall. |
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. |
From: Niall M. <nia...@ic...> - 2006-11-20 13:11:51
|
> > >I have just built and installed perfsuite 0.6.2 alpha5. I built it with > > >papi support and built it against papi 3.2.1. I am running on an amd > > >opteron with a perfctr patched SLES 2.6.5-7 kernel. Once built all the > > >perfsuite tests completed correctly. However when I try to run psrun I > > >get the following error: > > > > > > libpsrun fatal error: error reported by performance software layer > > > > > >I found on an earlier thread that this error was a > > >result of using a 2.6 kernel when there was no support for it. However > > >version 0.6.2 alpha 5 lists the 2.6 kernel. Any help or suggestions > > >would be much appreciated. > > > > >=20 > > You're correct, the 2.6 kernel is now supported. My guess about what's= =20 > > happening is that the events being selected by default are including=20 > > one that isn't available in PAPI 3.2.1. For your installation, the > > defaults should be in the file: > >=20 > > $PREFIX/share/perfsuite/xml/pshwpc/papi3_k8.xml > >=20 > > I would suggest running "psinv -p" to verify which PAPI events are > > available on your system and compare those with the events listed in > > the above file. If there is one that does not match, just comment it o= ut > > in the file and try again. If that fixes the problem, then please let = me > > know and I'll make the appropriate change in the distribution for the n= ext > > release. If it doesn't then advise of that as well and we can look a > > little closer to try and get you up and running. >=20 >=20 > 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 config= uration file=20 > 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.=20 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. Niall. |
From: Niall M. <nia...@ic...> - 2006-11-20 12:46:40
|
Hi Rick, > >I have just built and installed perfsuite 0.6.2 alpha5. I built it with > >papi support and built it against papi 3.2.1. I am running on an amd > >opteron with a perfctr patched SLES 2.6.5-7 kernel. Once built all the > >perfsuite tests completed correctly. However when I try to run psrun I > >get the following error: > > > > libpsrun fatal error: error reported by performance software layer > > > >I found on an earlier thread that this error was a > >result of using a 2.6 kernel when there was no support for it. However > >version 0.6.2 alpha 5 lists the 2.6 kernel. Any help or suggestions > >would be much appreciated. > > > > You're correct, the 2.6 kernel is now supported. My guess about what's > happening is that the events being selected by default are including > one that isn't available in PAPI 3.2.1. For your installation, the > defaults should be in the file: > > $PREFIX/share/perfsuite/xml/pshwpc/papi3_k8.xml > > I would suggest running "psinv -p" to verify which PAPI events are > available on your system and compare those with the events listed in > the above file. If there is one that does not match, just comment it out > in the file and try again. If that fixes the problem, then please let me > know and I'll make the appropriate change in the distribution for the next > release. If it doesn't then advise of that as well and we can look a > little closer to try and get you up and running. 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. Niall. |
From: Rick K. <rk...@nc...> - 2006-11-18 03:22:00
|
Niall, > I have just built and installed perfsuite 0.6.2 alpha5. I built it with > papi support and built it against papi 3.2.1. I am running on an amd > opteron with a perfctr patched SLES 2.6.5-7 kernel. Once built all the > perfsuite tests completed correctly. However when I try to run psrun I > get the following error: > > libpsrun fatal error: error reported by performance software layer > > I found on an earlier thread that this error was a > result of using a 2.6 kernel when there was no support for it. However > version 0.6.2 alpha 5 lists the 2.6 kernel. Any help or suggestions > would be much appreciated. > You're correct, the 2.6 kernel is now supported. My guess about what's happening is that the events being selected by default are including one that isn't available in PAPI 3.2.1. For your installation, the defaults should be in the file: $PREFIX/share/perfsuite/xml/pshwpc/papi3_k8.xml I would suggest running "psinv -p" to verify which PAPI events are available on your system and compare those with the events listed in the above file. If there is one that does not match, just comment it out in the file and try again. If that fixes the problem, then please let me know and I'll make the appropriate change in the distribution for the next release. If it doesn't then advise of that as well and we can look a little closer to try and get you up and running. Rick |
From: Niall M. <nia...@ic...> - 2006-11-17 15:43:48
|
Hi, I have just built and installed perfsuite 0.6.2 alpha5. I built it with papi support and built it against papi 3.2.1. I am running on an amd opteron with a perfctr patched SLES 2.6.5-7 kernel. Once built all the perfsuite tests completed correctly. However when I try to run psrun I=20 get the following error: libpsrun fatal error: error reported by performance software layer I found on an earlier thread that this error was a=20 result of using a 2.6 kernel when there was no support for it. However version 0.6.2 alpha 5 lists the 2.6 kernel. Any help or suggestions would be much appreciated.=20 Regards, Niall. --=20 -- | Niall Moran | Systems Administrator | Irish Centre for High-End Computing \niall dot moran at ichec dot ie -------------------------- |
From: Rick K. <rk...@nc...> - 2006-11-17 01:20:11
|
Xin, > a. Can I get a general conclusion about the performance of my code from the > two reports of psrun (see attachment) Not to sound cryptic, but the primary conclusion is that the report tells you what the hardware says it is doing during the run of your code. To get farther into it than that would probably require knowledge of the code itself, which you may be in the best position to have. There was a paper in Supercomputing ten years ago that is a nice discussion of the general utility of performance counters in program analysis. A Google search locates a copy of it here: http://cch.loria.fr/documentation/docSGI/perfex/index.html There is a manual that SGI put out that I think provides a very good introduction to approaching performance analysis with data such as that which PerfSuite provides. You might want to have a look at it to get started. Here is a link that seems to be active: http://techpubs.sgi.com/library/tpl/cgi-bin/browse.cgi?coll=linux&db=bks&cmd=toc&pth=/SGI_Developer/LX_AppTune There is an older manual also from SGI and specific to their Origin systems that provides more comprehensive information about general approaches. I think it's particularly good, the link for that is: http://techpubs.sgi.com/library/tpl/cgi-bin/browse.cgi?coll=0650&db=bks&cmd=toc&pth=/SGI_Developer/OrOn2_PfTune While neither of these manuals talk about PerfSuite, they're relevant for people using psrun anyway, whether in counting mode (like you are using) or profiling mode. > b. Why I get negative values in the output? What does this mean? This is an issue specific to the Itanium2 processor (that is what is in the Altix that you are using) that has been asked about before. Here's a pointer to a previous post to this list: http://sourceforge.net/mailarchive/forum.php?thread_id=9653918&forum_id=39162 Rick |
From: Xin J. <xj...@uc...> - 2006-11-16 17:24:57
|
Hi, I am a newcomer to use perfsuite and have run psrun to test my program. I found it is hard to analyze the output. My questions are: a. Can I get a general conclusion about the performance of my code from the two reports of psrun (see attachment) b. Why I get negative values in the output? What does this mean? Thanks, Xin -- ________________________________________ Xin Jin Inst.of Geophysics and Planetary Physics University of California Los Angeles 5845 Slichter Hall Los Angeles, CA 90095-4996, USA phone: (310) 825 4526 fax : (310) 206 3051 email: xj...@uc... |
From: Daniel T. <dt...@sg...> - 2006-11-14 09:26:15
|
Rick Kufrin wrote: > Dan, > >> I am trying to install perfsuite-0.6.2a5 on an SGI Altix running SLES 9 >> SP3 kernel 2.6.5-7. >> >> I was interested to use Psrun to get the Itanium native counters. But >> apparently this would only work with perfmon-1. Unfortunately I think ( >> but I can be wrong) that Perfmon-1 doesn't work with a 2.6 kernel. Is >> there anything I can do to overflow this issue ? > > > You're correct, the current release of PerfSuite provides direct > Perfmon support only for Perfmon 1, for the 2.4 kernels. An update to > IA64/Perfmon2 has been in the works, delayed mainly due to lack of > time, but it will be coming. > > There is a workaround, however. One can name Itanium2 native events > in PerfSuite configuration files that specify PAPI as the counter > access mechanism. The downside of this is that there is an extra > software layer to go through (PAPI), which may cause some additional > overhead depending on use, but should be serviceable. You have to > also install PAPI of course, > and configure PerfSuite to use it, but hopefully not too difficult. > > There is an example of such a configuration file that might help see > how this works. After installing PerfSuite, look at the file: > > $PREFIX/share/perfsuite/xml/pshwpc/papi3_ipc_itanium2.xml > > This shows use of Itanium-2 native events through PAPI. Both counting > and profiling runs with native events should work just fine. > > Rick Hi Rick, Thanks very much for your reply. It just worked fine the way you said. Daniel |
From: Rick K. <rk...@nc...> - 2006-11-14 01:00:57
|
Dan, > I am trying to install perfsuite-0.6.2a5 on an SGI Altix running SLES 9 > SP3 kernel 2.6.5-7. > > I was interested to use Psrun to get the Itanium native counters. But > apparently this would only work with perfmon-1. Unfortunately I think ( > but I can be wrong) that Perfmon-1 doesn't work with a 2.6 kernel. Is > there anything I can do to overflow this issue ? You're correct, the current release of PerfSuite provides direct Perfmon support only for Perfmon 1, for the 2.4 kernels. An update to IA64/Perfmon2 has been in the works, delayed mainly due to lack of time, but it will be coming. There is a workaround, however. One can name Itanium2 native events in PerfSuite configuration files that specify PAPI as the counter access mechanism. The downside of this is that there is an extra software layer to go through (PAPI), which may cause some additional overhead depending on use, but should be serviceable. You have to also install PAPI of course, and configure PerfSuite to use it, but hopefully not too difficult. There is an example of such a configuration file that might help see how this works. After installing PerfSuite, look at the file: $PREFIX/share/perfsuite/xml/pshwpc/papi3_ipc_itanium2.xml This shows use of Itanium-2 native events through PAPI. Both counting and profiling runs with native events should work just fine. Rick |
From: Daniel T. <dt...@sg...> - 2006-11-13 17:21:53
|
Hi, I am trying to install perfsuite-0.6.2a5 on an SGI Altix running SLES 9 SP3 kernel 2.6.5-7. I was interested to use Psrun to get the Itanium native counters. But apparently this would only work with perfmon-1. Unfortunately I think ( but I can be wrong) that Perfmon-1 doesn't work with a 2.6 kernel. Is there anything I can do to overflow this issue ? Thanks in advance, Daniel Thomas SGI |
From: Rick K. <rk...@nc...> - 2006-10-20 13:46:06
|
Don, On Wed, 18 Oct 2006, Don DeSota wrote: > I am getting the following message running psrun. > > psrun fatal error: error reported by performance software layer This is somewhat of a "catch-all" error that occurs when the underlying software (of which PAPI is one instance) has a failure. At the moment, the specific failure (error code) is not passed up to the uppermost level. That is, the psrun command only learns that something is wrong, but not anything more detailed. It may help to know which version of PAPI you are using (release vs. CVS) and also what kernel patch/version you have applied (perfctr, perfmon). > I have installed perfsuite with papi, tdom/tcl. All PAPI and perfsuite > tests pass. I'm running an athlon-x2 with a generic kernel at 2.6.??. Any > suggestions on what to try now? There is a configure-time option to PerfSuite: --enable-debug, that can be specified whose purpose is to track the internal operation of the libraries that are involved. You might try: - make clean - reconfigure identically, but add --enable-debug (your original configure options should be stored in the file "config.log" in the directory where PerfSuite was built - make - run the PerfSuite test suite with "make -s check", and note if PAPI-related tests are marked as "ok" or "SKIPPED" - run psrun on your program, but set the environment variable PS_DEBUG=3 and capture the output There should be a lot of information displayed, and hopefully some information towards the end that may help focus in on where things are failing, which would be helpful to see. Additionally, the output of the command "psinv" and "psinv -x", along with the contents of the file "config.log" which is created at configure time, can help see your machine/build environment. Rick |
From: Don D. <de...@us...> - 2006-10-18 17:24:09
|
I am getting the following message running psrun. psrun fatal error: error reported by performance software layer I have installed perfsuite with papi, tdom/tcl. All PAPI and perfsuite tests pass. I'm running an athlon-x2 with a generic kernel at 2.6.??. Any suggestions on what to try now? |
From: Rick K. <rk...@nc...> - 2006-10-09 23:54:28
|
Luca, Thanks for letting me know that things turned out OK. I'm thinking that=20 the issue of link-time directories should be improved in PerfSuite's build= =20 system but am glad you were able to make things work. The PAPI (and in this case, perfctr) library directories are set up by the= =20 PerfSuite "psenv" commands, but that only helps *after* PerfSuite has been= =20 installed, not during configuration/build. Rick On Mon, 9 Oct 2006, luc...@ex... wrote: > Rick, > > I placed $PAPILIB directory in LD_LBRARY_PATH and runs. > Thanks for your help. > Luca > > <-----Messaggio Originale-----> >> From: Rick Kufrin >> Sent: 9/10/2006 3:19:14 PM >> To: luc...@ex... >> Cc: per...@li... >> Subject: Re: [PerfSuite-users] Installation of Perfsuite >> >> Luca, >> >>> I tried to install Perfsuite 0.6.2a5. >>> I patched the kernel, installed tDOM, ExPat, PAPI3 and made all the >>> tests. >>> With the opened device /dev/perfctr, perfex -i returns a well-formed >>> result, not an error. >> >> Sounds like you're almost there. I assume running perfex on an > executable >> (even "ls") works OK. >> >>> >>> All is ok but when I launch ./configure --prefix=3D/home/luca/perfsuite >>> --with-tdom=3D/home/luca/tDOM/lib --with-papi=3D/home/luca/papi it > returns >>> an error to configure PAPI support. >>> >>> In the config.log i f ound this error: >>> >>> libperfctr.so.5, needed by libpapi.so, not found (try with -rapth or >>> -rpath-link) >>> >>> but in the directory /home/luca/papi/lib/ exists libpctr.so.5 also > with >>> libpapi.so and libpapi.a. >> >> It's a little difficult to say without knowing how your system is laid >> out. It may be helpful to have a look at the config.log file in its >> entirety - can you send that? >> >> Also, does a simple PAPI program (outside of the PAPI test suite) link > an >> run properly? It doesn't have to be complex, something like: >> >> #include >> >> main() >> { >> PAPI_library_init(PAPI_VER_CURRENT); >> } >> >> $ cc test.c -I$PAPIDIR/include -L$PAPIDIR/lib -lpapi >> >> should be enough to test. More than likely, placing libraries in >> directories that are in the linker search path (LD_LIBRARY_PATH) will >> probably get you up and running. >> >> Rick >> >> . >> > > > <P><p><font face=3D"Arial, Helvetica, sans-serif" size=3D"2" style=3D"fon= t-size:13.5px">____________________________________________________________= ___<BR><table border=3D"0" cellpadding=3D"0" cellspacing=3D"0"><tr><td vali= gn=3D"top" align=3D"left"><font face=3D"Arial, Helvetica, sans-serif" size= =3D"2" style=3D"font-size:14.5px"><BR><BODY><a href=3D"http://ad.it.doublec= lick.net/clk;48625085;14254949;t?http://meetic.excite.it">Trova l=92amore c= on Meetic: l=92iscrizione =E8 gratuita!</a> > </BODY></font></td></tr></table></font> |
From: Rick K. <rk...@nc...> - 2006-10-09 13:19:25
|
Luca, > I tried to install Perfsuite 0.6.2a5. > I patched the kernel, installed tDOM, ExPat, PAPI3 and made all the > tests. > With the opened device /dev/perfctr, perfex -i returns a well-formed > result, not an error. Sounds like you're almost there. I assume running perfex on an executable (even "ls") works OK. > > All is ok but when I launch ./configure --prefix=/home/luca/perfsuite > --with-tdom=/home/luca/tDOM/lib --with-papi=/home/luca/papi it returns > an error to configure PAPI support. > > In the config.log i f ound this error: > > libperfctr.so.5, needed by libpapi.so, not found (try with -rapth or > -rpath-link) > > but in the directory /home/luca/papi/lib/ exists libpctr.so.5 also with > libpapi.so and libpapi.a. It's a little difficult to say without knowing how your system is laid out. It may be helpful to have a look at the config.log file in its entirety - can you send that? Also, does a simple PAPI program (outside of the PAPI test suite) link an run properly? It doesn't have to be complex, something like: #include <papi.h> main() { PAPI_library_init(PAPI_VER_CURRENT); } $ cc test.c -I$PAPIDIR/include -L$PAPIDIR/lib -lpapi should be enough to test. More than likely, placing libraries in directories that are in the linker search path (LD_LIBRARY_PATH) will probably get you up and running. Rick |
From: <luc...@ex...> - 2006-10-09 07:12:39
|
Hi! I tried to install Perfsuite 0.6.2a5. I patched the kernel, installed tDOM, ExPat, PAPI3 and made all the tests. With the opened device /dev/perfctr, perfex -i returns a well-formed result, not an error. All is ok but when I launch ./configure --prefix=/home/luca/perfsuite --with-tdom=/home/luca/tDOM/lib --with-papi=/home/luca/papi it returns an error to configure PAPI support. In the config.log i f ound this error: libperfctr.so.5, needed by libpapi.so, not found (try with -rapth or -rpath-link) but in the directory /home/luca/papi/lib/ exists libpctr.so.5 also with libpapi.so and libpapi.a. Can you help me? Thanks, Luca <P><p><font face="Arial, Helvetica, sans-serif" size="2" style="font-size:13.5px">_______________________________________________________________<BR><table border="0" cellpadding="0" cellspacing="0"><tr><td valign="top" align="left"><font face="Arial, Helvetica, sans-serif" size="2" style="font-size:14.5px"><BR><BODY><a href="http://ad.it.doubleclick.net/clk;48625085;14254949;t?http://meetic.excite.it">Trova lamore con Meetic: liscrizione è gratuita!</a> </BODY></font></td></tr></table></font> |
From: Rick K. <rk...@nc...> - 2006-09-20 00:03:33
|
Dawei, > But now I encoutered a new problem of monitor a appliction program. > For example > psrun -f a.exe -p > the a.exe here is a sever lisenter program for network connection,if there is a connection from a remote machine,there will be a new process of a work for this connection.i want to profile the cpu usage and cahce infomantion of a.exe in a preriod. but when the a.exe finished ,I don not found the profile infomation (xml file).I donnot know why. > > by the way.I can monitor a simple program,and got the report xml file. > It's hard to say exactly what's going on here. The "-f" and "-p" options work very differently, the first attempts to track forked processes while the second attempts to track created threads. It's a totally different mechanism used for each. One approach that people don't usually try but tends to provide the most predictable results is to abandon using psrun altogether and instead insert calls to the PerfSuite API into the program they want to measure. The API is pretty easy to use, consisting (primarily) of the routines: int ps_hwpc_init(void); int ps_hwpc_start(void); int ps_hwpc_stop(char *filename); int ps_hwpc_shutdown(void); The above routines are all that is used by psrun, which is really just a driver program that sets things up so that these functions can be called. There are several examples in the installed "examples" directory that can help get started with using the API (again, when using the API psrun is no longer necessary). Probably the best place to look is the "cpi" example directory, which contains several variants of a "calculate Pi" program: serial, pthreads, OpenMP, MPI (C and Fortran). Rick |
From: liudawei <dbm...@ya...> - 2006-09-18 04:03:39
|
I am sorry for ask so many simple question, and thanks a lot to Rick Kufrin for his kindness for giving anawer.Now everything is ok. But now I encoutered a new problem of monitor a appliction program. For example psrun -f a.exe -p the a.exe here is a sever lisenter program for network connection,if there is a connection from a remote machine,there will be a new process of a work for this connection.i want to profile the cpu usage and cahce infomantion of a.exe in a preriod. but when the a.exe finished ,I don not found the profile infomation (xml file).I donnot know why. by the way.I can monitor a simple program,and got the report xml file. best regards Dawei Liu --------------------------------- 雅虎免费邮箱-3.5G容量,20M附件 |
From: Rick K. <rk...@nc...> - 2006-09-17 15:01:45
|
Dawei, I think you may have tried to build tDOM in its top-level directory,=20 rather than in the "unix" subdirectory. From the PerfSuite INSTALL=20 instructions: --------------------- tDOM is very simple to build from the distribution. All you should=20 have to do is to change to the "unix" subdirectory, decide where you want tDOM installed ($TDOMDIR below), and enter the commands: ../configure --prefix=3D$TDOMDIR make Please note that the tDOM "configure" command is executed from the=20 parent directory (that is, the ".." in the above example is correct). Your=20 working directory should be "unix" in the tDOM source tree when you build the software. ---------------------- There is additional information specific to tDOM on Itanium 2 that you=20 might want to review before attempting a build. If there is anything=20 unclear in PerfSuite's INSTALL file, please let me know so that it can be= =20 improved. Rick p.s. please send email to the PerfSuite SourceForge mailing list rather=20 than to me directly. This makes it easier to manage and also can help=20 other people find information from prior posts which are archived at SF. On Sun, 17 Sep 2006, liudawei wrote: > Thank you very much. you are right. > I have download the tDom,and trying to make.I got the new problem like th= is > > "make: *** No rule to make target `xmlsimple.o', needed by `libtdom0.8.0= =2Eso'. Stop." > > Rick Kufrin <rk...@nc...> =D0=B4=B5=C0=A3=BA > Dawei - this might be simple to fix: the error is coming from not having > the PerfSuite library directory in your LD_LIBRARY_PATH environment > variable. The "usual" procedure is to first: > > # source $PREFIX/bin/psenv.sh > > ...where $PREFIX corresponds to the directory you supplied to configure > with the "--prefix=3D" option (or /usr/local if you didn't supply that > option). The "psenv" script arranges for several environment variables to > be set properly to run the PerfSuite tools successfully. > > I am guessing that you did not build PerfSuite with Tcl/tDOM support > (because the psprocess command does not appear in your bin directory). > You might want to reconfigure and rebuild PerfSuite with these extra > pieces of supporting software (as well as PAPI, if that is also missing > from your build). You can find information about obtaining these pieces > in the INSTALL file in the PerfSuite distribution. > > Rick > > On Sun, 17 Sep 2006, liudawei wrote: > >> I have installed perfsuite successfully. and using make -s check show th= at all the test is ok. >> when I switch to the install directory /usr/lcoal/bin >> I only found 4 files :psenv.csh psenv.sh psinv psrun >> psin can run success and report the machine info. >> but when i try to run psrun I got the following message >> ERROR: ld.so: object 'libpsrun.so.0' from LD_PRELOAD cannot be preloaded= : ignored. >> >> Can anyone help me? >> >> Best reagard >> Dawei >> > > > > --------------------------------- > Mp3=B7=E8=BF=F1=CB=D1-=D0=C2=B8=E8=C8=C8=B8=E8=B8=DF=CB=D9=CF=C2 |
From: Rick K. <rk...@nc...> - 2006-09-17 14:31:59
|
Dawei - this might be simple to fix: the error is coming from not having the PerfSuite library directory in your LD_LIBRARY_PATH environment variable. The "usual" procedure is to first: # source $PREFIX/bin/psenv.sh ...where $PREFIX corresponds to the directory you supplied to configure with the "--prefix=" option (or /usr/local if you didn't supply that option). The "psenv" script arranges for several environment variables to be set properly to run the PerfSuite tools successfully. I am guessing that you did not build PerfSuite with Tcl/tDOM support (because the psprocess command does not appear in your bin directory). You might want to reconfigure and rebuild PerfSuite with these extra pieces of supporting software (as well as PAPI, if that is also missing from your build). You can find information about obtaining these pieces in the INSTALL file in the PerfSuite distribution. Rick On Sun, 17 Sep 2006, liudawei wrote: > I have installed perfsuite successfully. and using make -s check show that all the test is ok. > when I switch to the install directory /usr/lcoal/bin > I only found 4 files :psenv.csh psenv.sh psinv psrun > psin can run success and report the machine info. > but when i try to run psrun I got the following message > ERROR: ld.so: object 'libpsrun.so.0' from LD_PRELOAD cannot be preloaded: ignored. > > Can anyone help me? > > Best reagard > Dawei > |
From: Rick K. <rk...@nc...> - 2006-09-17 14:25:42
|
Dawei - I am guessing from your followup message that you've resolved this problem. These are functions from the Perfmon userspace library, libpfm. One thing I should note is that PerfSuite does not yet have direct support for perfmon/libpfm on 2.6-based kernels (however, the PAPI interface, which does support libpfm for that series, provides that functionality). Rick On Sun, 17 Sep 2006, liudawei wrote: > I using Ia-64 server. in the process of make, I encontered the follow error message: > > psinv.o(.text+0x2df2): In function `print_native_events': > /home/ftpuser/perfsuite-0.6.2a5/tools/psinv/psinv.c:839: undefined reference to `pfm_get_first_event' > psinv.o(.text+0x2e42):/home/ftpuser/perfsuite-0.6.2a5/tools/psinv/psinv.c:842: undefined reference to `pfm_get_next_event' > psinv.o(.text+0x2e82):/home/ftpuser/perfsuite-0.6.2a5/tools/psinv/psinv.c:854: undefined reference to `pfm_get_first_event' > psinv.o(.text+0x2f32):/home/ftpuser/perfsuite-0.6.2a5/tools/psinv/psinv.c:854: undefined reference to `pfm_get_next_event' > psinv.o(.text+0x3102):/home/ftpuser/perfsuite-0.6.2a5/tools/psinv/psinv.c:839: undefined reference to `pfm_get_first_event' > psinv.o(.text+0x31b2):/home/ftpuser/perfsuite-0.6.2a5/tools/psinv/psinv.c:854: undefined reference to `pfm_get_next_event' > > > I have patched the libpfm 2.x and my linux CONFIG_PERFMON=y > > who can help me? > > Best reagards > Dawei Liu > > |