Egorodet

PerfStudio 2 for Compute Shader debugging in Dispatch pipeline (GPGPU scenario)

Discussion created by Egorodet on Mar 12, 2010
Latest reply on Aug 10, 2011 by virtazim
Discuss possibility of using PerfStudio 2 Compute Shader debugging in Dispatch pipeline, without Graphics pipeline

Hi!

I'm using Compute Shaders 5 to develop GPGPU application which has no Graphics pipeline and CS is running in Dispatch pipeline only. I'm very interested in DX11 Compute Shader debugging capabilities provided by GPU PerfStudio 2.X and wondering if it is possible to use it for applications with Dispatch pipeline.

I've tried PerfStudio 2.1 to debug BasicCompute11 sample from DX SDK (February 2010), but didn't succeed - client reported error "Unable to attach to current application. Please make sure it is using a supported graphics API", while server printed these messages:

GPU PerfStudio Server - Version V2.1.719

Message: Server        : Using Logfile: D:/GPUPerfStudio2.1/Server-Win32/pslog.txt

Message: Server        : Succesfully enabled DX Peformance Counters in Driver

Message: Server        : Available Wrappers:

Message: Server        :    DX10Server.dll      V2.1.719        DX10

Message: Server        :    DX11Server.dll      V2.1.719        DX11

Message: Server        :    GLServer.dll        V2.1.719        OpenGL

 

Message: Server        : Starting web server on port 80

Message: Server        : About to launch: C:\Program Files\Microsoft DirectX SDK (February 2010)\Samples\C++\Direct3D11\Bin\x86\BasicCompute11.exe

Message: Server        : Params:

Message: Server        : Working Directory:

Creating device...Message: Server        :   0: 127.0.0.1  - /Process.xml

done

Creating Compute Shader...done

Creating buffers and filling them with initial data...done

Creating buffer views...done

Running Compute Shader...done

Verifying against CPU result...succeeded

Cleaning up...

Message: Server        :   1: 127.0.0.1  - /Process.xml

Message: Server        :   2: 127.0.0.1  - /Process.xml

Message: Server        :   3: 127.0.0.1  - /Process.xml

Message: Server        :   4: 127.0.0.1  - /Process.xml

Message: Server        :   5: 127.0.0.1  - /Process.xml

Message: Server        :   6: 127.0.0.1  - /Process.xml

...
Is it still possible to use PerfStudio 2.1 for CS debuigging in Dispatch pipeline, may be with some worarounds? Are you going to support this scenarion in future versions of PerfStudio?

Outcomes