Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ptp-dev] TAU Plugin Status

Greetings,

In the current version of the plugins the PAPI functionality is only integrated with the TAU performance analysis elements.  The location of PAPI passed to the selector plugin is taken from a TAU makefile selected in the performance plugin.  When no such makefile is available, neither is the PAPI plugin.  You can access it through the following steps.

Configure and build TAU with -papi=, -MULTIPLECOUNTERS and -pdt= (look here http://wiki.eclipse.org/PTP/designs/perf_tools_framework/TAU for more information on how to do this)
In Eclipse (in the C++ or Fortran perspective) go to Run->Profile...  This will open the profile launch configuration window.  Note that this can also be reached via the Profile button, which should show up next to the Run and Debug buttons after the TAU plugins are installed.
In the launch configuration Window create a new Launch configuration (if you make a parallel launch configuration, be sure the PTP runtime has already been initialized or else this bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=163289 may cause problems). 
Set any required fields (such as the project and build configuration to be instrumented) and go to the TAU tab.
On the TAU tab you should be able to check the PAPI box which will reduce the list of available TAU configurations to those configured with PAPI.  It will also enable the PAPI selection button.
Note that presently you have to choose to select either Preset or Native counters outside of the selector plugin itself.  Both options should be available within the PAPI selection window eventually.
Launch the PAPI selector with the "Select PAPI Counters" button.  Each available counter will be shown in the resulting list.  Put a check next to the counters you wish to use.  When other counters are unavailable with your current selection their check-box will be marked with a dash, or greyed out, and you will be unable to select them until you uncheck the conflicting counters.
When you apply your selection the selected counters will be put in this launch configuration's Environment (using TAU specific environment variable names in this case).  You may need to refresh the configuration by closing and reopening it before the changes to the Environment settings will be visible, but they will be applied when it is run regardless.

Please let me know if you have any questions or if anything goes amiss.

Note that the PAPI selection tool is already a distinct plugin, it is just tightly coupled with the TAU stuff in this case.  It would be fairly easy for me to make a demo-implementation of the plugin which could be accessed from a menu.  I will probably need to do something like this anyway to make further development of the PAPI plugin easier.  However this would merely print out the list of selected counters.  It is the job of the plugins calling the PAPI selector to do something useful with the counters it returns ( e.g. associate them with tool-specific names and stick them in the launcher's environment).

Regards,
Wyatt

On 10/11/07, Dan Terpstra < terpstra@xxxxxxxxxxxx> wrote:

Wyatt –

I think we now have a successful installation of the PTP stuff on our Core2 cluster. At least Eclipse shows the MPI and OpenMP menu items and tool bar buttons.

I can even go to Window->Show View->Other and see the Performance Data Manager plugin with the TAU icon.

However, I'm stymied as to how to locate the PAPI plugin.

Can you help? What am I missing? What should I read?

Thanks,

- dan

 


From: ptp-dev-bounces@xxxxxxxxxxx [mailto: ptp-dev-bounces@xxxxxxxxxxx] On Behalf Of wspear
Sent: Thursday, October 04, 2007 5:39 PM
To: Parallel Tools Platform general developers
Subject: [ptp-dev] TAU Plugin Status

 

Greetings,

Thanks to Beth's diligent efforts the current set of performance analysis plugins are now up on CVS.  The improvements and various bugfixes are listed over on the eclipsezilla entry ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=168292).  Quite a lot has changed since the last CVS commit but one of the most exciting new features is the ability for the user to specify his or her own performance tools, weather they are compiler wrappers, execution utilities of performance data analysis tools, for use in a basic performance analysis work-flow.

I intend to have an updated entry on the PTP wiki soon detailing the new functionality.  The current entry (http://wiki.eclipse.org/PTP/designs/perf_tools_framework/TAU ) remains accurate with respect to the TAU-specific functionality.

There is still a lot to be done and things are being added and adjusted fairly quickly.  The next patch should include better support for specifying the output and analysis of performance data.  Additional features in the works include support for database-enabled storage and display of profile data types in addition to TAU's, support for  tool-specific environment variable configuration, EFS compatibility and user defined tool configuration tabs in the launch configuration manager.

If anyone wants help installing and using the plugins please let me know.  Questions, comments or feedback on the performance plugins are encouraged.  Development is quite flexible at this point so this is a good time to provide suggestions.

Regards,
Wyatt Spear


_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev



Back to the top