PGI User Forum
 SearchSearch   MemberlistMemberlist     RegisterRegister   ProfileProfile    Log inLog in 

CUDA-x86.

Pgprof and accelerators

 
Post new topic   Reply to topic    PGI User Forum Forum Index -> Debugging and Profiling
View previous topic :: View next topic  
Author Message
TheMatt



Joined: 06 Jul 2009
Posts: 306
Location: Greenbelt, MD

PostPosted: Mon Jan 25, 2010 12:31 pm    Post subject: Pgprof and accelerators Reply with quote

I decided to try out pgprof with an accelerated kernel mainly for my own education and to see if there are bottlenecks I'm missing. I followed the example in the PGI Tools document:
Code:
> make runsorad-vector32.exe
pgfortran -fast -r4 -Mextend -Mpreprocess -Ktrap=fp -ta=nvidia,time -Minfo=ccff -c src/sorad.vector32.f
pgfortran -fast -r4 -Mextend -Mpreprocess -Ktrap=fp -ta=nvidia,time -Minfo=ccff -c src/sorad.orig.noaero.donottouch.f
pgfortran -fast -r4 -Mextend -Mpreprocess -Ktrap=fp -ta=nvidia,time -Minfo=ccff -c src/driver-check.f90
pgfortran -fast -r4 -Mextend -Mpreprocess -Ktrap=fp -ta=nvidia,time -Minfo=ccff sorad.vector32.o sorad.orig.noaero.donottouch.o driver-check.o -o runsorad-vector32.exe
> pgcollect -time runsorad-vector32.exe
...output from program...
> ls pg*out
pgpacc.out  pgprof.out
> pgprof -exe runsorad-vector32.exe

At that point, things diverge. Instead of seeing the two Accelerator columns as shown in Figure 15.11, I get the normal two-column mode. Of course, that also means that nothing of my GPU kernel is displayed as well. Likewise the Accelerator "undertab" is ever-blank.

Yet, there is that non-zero-size pgpacc.out file with cryptic information in it. Is there an extra flag/switch I need to use to get pgprof to read the accelerator results?

Matt
Back to top
View user's profile
mkcolg



Joined: 30 Jun 2004
Posts: 5952
Location: The Portland Group Inc.

PostPosted: Tue Jan 26, 2010 6:59 am    Post subject: Reply with quote

Hi Matt,

It might be a conflict with the "time" option and pgcollect. Both use the same profiling routine to capture the GPU timing info. Instead of being directed to the pgprof.out file, it may be going to stderr. Try removing "time" from "-ta".

Thanks,
Mat
Back to top
View user's profile
TheMatt



Joined: 06 Jul 2009
Posts: 306
Location: Greenbelt, MD

PostPosted: Tue Jan 26, 2010 7:13 am    Post subject: Reply with quote

mkcolg wrote:
Hi Matt,

It might be a conflict with the "time" option and pgcollect. Both use the same profiling routine to capture the GPU timing info. Instead of being directed to the pgprof.out file, it may be going to stderr. Try removing "time" from "-ta".

Ayup, that was it! I guess that means a minor bug report for the PGI Tools document which specifically states you can do both pgcollect and "time".

Thanks,
Matt

(Preview: My next post/thread will be on pgcollect and OProfile...though I'm guessing the fault is with OProfile and not pgcollect.)
Back to top
View user's profile
mkcolg



Joined: 30 Jun 2004
Posts: 5952
Location: The Portland Group Inc.

PostPosted: Tue Jan 26, 2010 3:08 pm    Post subject: Reply with quote

Hi Matt,

Quote:
I guess that means a minor bug report for the PGI Tools document which specifically states you can do both pgcollect and "time".
Well, the doc is correct, it's pgcollect that has the bug.

Thanks,
Mat
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    PGI User Forum Forum Index -> Debugging and Profiling All times are GMT - 7 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © phpBB Group