OpenCL NVIDIA Command Line Profiling Unable to profile OpenCL program with NVIDIA Command Line Profi
Hi,
I have read "Compute Command Line Profiler" document and I have set the following environment variables.
COMPUTE_PROFILE=1
COMPUTE_PROFILE_CONFIG=config_file
COMPUTE_PROFILE_CSV=0
COMPUTE_PROFILE_LOG=log_file

In the config_file I have tested with two counters: instructions and branch.
The problem is that I don't get any output, the file is not even created. Nevertheless, if I run a CUDA Program I get correct profiling output with same configuration.

I am using CUDA Toolkit 5 prerelease and driver version 302.59.
The board I am using is a GeForce GTX 285.

Thanks in advance
Hi,

I have read "Compute Command Line Profiler" document and I have set the following environment variables.

COMPUTE_PROFILE=1

COMPUTE_PROFILE_CONFIG=config_file

COMPUTE_PROFILE_CSV=0

COMPUTE_PROFILE_LOG=log_file



In the config_file I have tested with two counters: instructions and branch.

The problem is that I don't get any output, the file is not even created. Nevertheless, if I run a CUDA Program I get correct profiling output with same configuration.



I am using CUDA Toolkit 5 prerelease and driver version 302.59.

The board I am using is a GeForce GTX 285.



Thanks in advance

#1
Posted 05/28/2012 11:11 AM   
Strange, that looks like the right environment variables to set.
I just started using the command line profiler in Linux for CUDA Toolkit 4.2 this week.
The other difference is that I specified the full-path for my config_file, and I didn't set the *_CSV or *_LOG environment variables, letting those select the defaults.
But other than you using a pre-release Toolkit version as a possible cause, are you sure the current working directory is writable?
Strange, that looks like the right environment variables to set.

I just started using the command line profiler in Linux for CUDA Toolkit 4.2 this week.

The other difference is that I specified the full-path for my config_file, and I didn't set the *_CSV or *_LOG environment variables, letting those select the defaults.

But other than you using a pre-release Toolkit version as a possible cause, are you sure the current working directory is writable?

Tim Mattox

#2
Posted 05/30/2012 08:46 PM   
Yes, I have permissions to write on that directory because executable is generated on the same directory.
Also I have proved an absolute path as log_file and config_file environment variables.
Yes, I have permissions to write on that directory because executable is generated on the same directory.

Also I have proved an absolute path as log_file and config_file environment variables.

#3
Posted 05/31/2012 09:57 AM   
Scroll To Top