Difference between revisions of "Keeneland"
| Line 5: | Line 5: | ||
We'll have a module for TAU setup shortly but for now, setup your environment this way: | We'll have a module for TAU setup shortly but for now, setup your environment this way: | ||
| − | |||
%> export PATH=/nics/c/home/biersdor/tau2/x86_64/bin/:$PATH | %> export PATH=/nics/c/home/biersdor/tau2/x86_64/bin/:$PATH | ||
%> export LD_LIBRARY_PATH=/nics/c/home/biersdor/tau2/x86_64/lib/:$LD_LIBRARY_PATH | %> export LD_LIBRARY_PATH=/nics/c/home/biersdor/tau2/x86_64/lib/:$LD_LIBRARY_PATH | ||
| − | == Compiling with == | + | == Compiling with TAU == |
| − | Details at: | + | Details at: [http://www.cs.uoregon.edu/research/tau/docs/newguide/bk01ch01s02.html TAU's userguide] |
| − | But the idea is replace your compiler with the TAU wrapper compilers, ie '''gcc''' => '''tau_cc.sh''', gfortran => '''tau_f90.sh''' etc... | + | But the basic idea is to replace your compiler with the TAU wrapper compilers, ie '''gcc''' => '''tau_cc.sh''', gfortran => '''tau_f90.sh''' etc... |
== Running with tau_exec == | == Running with tau_exec == | ||
| − | For a quick | + | For a quick profile/trace try the '''tau_exec''' [http://www.cs.uoregon.edu/research/tau/docs/newguide/re17.html script]. |
| Line 28: | Line 27: | ||
The '''-T serial''' specifies with TAU configuration to use, you can omit this for MPI applications and run: | The '''-T serial''' specifies with TAU configuration to use, you can omit this for MPI applications and run: | ||
| − | |||
| − | |||
=== Trouble-shooting === | === Trouble-shooting === | ||
| Line 49: | Line 46: | ||
== Running OpenCL applications == | == Running OpenCL applications == | ||
| − | Use | + | Use '''tau_exec''' as well: |
| + | |||
| + | %> tau_exec -T serial -opencl ./SGEMM | ||
== CUpti and PAPI == | == CUpti and PAPI == | ||
Coming soon... | Coming soon... | ||
Revision as of 19:31, 25 January 2011
Contents
Guide for using TAU on Keeneland
Setting up environment
We'll have a module for TAU setup shortly but for now, setup your environment this way:
%> export PATH=/nics/c/home/biersdor/tau2/x86_64/bin/:$PATH %> export LD_LIBRARY_PATH=/nics/c/home/biersdor/tau2/x86_64/lib/:$LD_LIBRARY_PATH
Compiling with TAU
Details at: TAU's userguide
But the basic idea is to replace your compiler with the TAU wrapper compilers, ie gcc => tau_cc.sh, gfortran => tau_f90.sh etc...
Running with tau_exec
For a quick profile/trace try the tau_exec script.
Running CUDA applications
Both CUDA and OpenCL are instrumented dynamically through library preloading, use the tau_exec script to run the CUDA application:
%> tau_exec -T serial -cuda ./Stencil2D
The -T serial specifies with TAU configuration to use, you can omit this for MPI applications and run:
Trouble-shooting
- CPU side looks fine but no GPU profile/trace generated.
This is likely because there is no cudaThreadExit() call at the end the application. By placing one there this will signal TAU that the applications CUDA accelerated section is finished and it can go ahead and write out the profile/trace.
Fix: Place cudaThreadExit() at the end of the application.
- Receiving Error calculating kernel event [start|stop], error #: 33. during execution.
This means that CUDA could not retrieve the event object at synchronization. Try placing the synchronize event right after the kernel is launched. In some cases no configuration of kernel launches/synchronization points will suffice, and although this one kernel could not be tracked any other ones taking place in the application should be tracked correctly.
Fix: Try placing a synchronization called right after the kernel launch.
Running OpenCL applications
Use tau_exec as well:
%> tau_exec -T serial -opencl ./SGEMM
CUpti and PAPI
Coming soon...
