[petsc-dev] call stack

2012-06-20 Thread Luigia Ambrosio
Hi all I'm interested in using PETSC with CUDA. I just downloaded and installed the developer version and I was testing the example #1 ($HOME/petsc-dev/src/vec/vec/examples/tutorials) to compute the norm of a vector. I would like to compare PETSC without cuda and with cuda. Is there a way to

[petsc-dev] call stack

2012-06-20 Thread Aron Ahmadia
Have you tried passing -log_summary to the command line? A On Wed, Jun 20, 2012 at 11:32 AM, Luigia Ambrosio ambrosio.luigia at gmail.com wrote: Hi all I'm interested in using PETSC with CUDA. I just downloaded and installed the developer version and I was testing the example #1

[petsc-dev] call stack

2012-06-20 Thread Luigia Ambrosio
Yes but it's not enough! I nedd the stack of the called methods and kernels. I just sent you my modified ex11 and the results of ./ex11 -log_summary thanks again Luigia Ambrosio Il giorno 20/giu/2012, alle ore 10:45, Aron Ahmadia ha scritto: Have you tried passing -log_summary to the

[petsc-dev] call stack

2012-06-20 Thread Matthew Knepley
On Wed, Jun 20, 2012 at 3:18 AM, Luigia Ambrosio ambrosio.luigia at gmail.comwrote: Yes but it's not enough! I nedd the stack of the called methods and kernels. I just sent you my modified ex11 and the results of ./ex11 -log_summary Use the debugger. Its the easiest way to get a stack.

[petsc-dev] call stack

2012-06-20 Thread Barry Smith
On Jun 20, 2012, at 4:18 AM, Luigia Ambrosio wrote: Yes but it's not enough! I nedd the stack of the called methods and kernels. I just sent you my modified ex11 and the results of ./ex11 -log_summary ex11.c log_summary thanks again gprof? Or the developer tools that Intel sells or

[petsc-dev] call stack

2012-06-20 Thread John Fettig
You can use hpctoolkit to profile the cpu portion, it does exactly what you are asking. To profile the cuda portion, you will have to use nvidia's visual profiler. John On Wed, Jun 20, 2012 at 4:32 AM, Luigia Ambrosio ambrosio.luigia at gmail.com wrote: Hi all I'm interested in using PETSC