mirror of https://github.com/wolfpld/tracy.git synced 2026-08-07 13:59:17 +00:00

Files

Basil Milanich 4ccaea9f08 Expand repro: multiple graphs, multiple kernels, interleaved launches

Tests:
- Two distinct graphs (different graphIds) on the same stream
- Graph A: kernel + memcpy + kernel (3 nodes)
- Graph B: scale + add + scale (3 nodes)
- 5 interleaved launches of each, stressing the graphId cache
- Expected 30 graph GPU zones total

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-04-06 11:54:08 -05:00

Makefile

Fix CUDA Graph GPU zones with proper cuGraphLaunch correlation

2026-04-06 11:03:58 -05:00

README.md

Add CUDA Graph GPU zone repro

2026-03-24 09:37:50 -05:00

repro.cu

Expand repro: multiple graphs, multiple kernels, interleaved launches

2026-04-06 11:54:08 -05:00

README.md

Tracy CUDA Graph GPU Zone Repro

Demonstrates that unpatched Tracy fails to show GPU zones for kernels launched via CUDA Graphs (cudaGraphLaunch).

Root cause

When kernels are launched through CUDA Graphs, CUPTI delivers CONCURRENT_KERNEL and MEMCPY activity records but no corresponding API callback fires for the individual kernel launches. Tracy's matchActivityToAPICall() always fails, and matchError() silently drops every GPU zone.

Build and run

make
./repro

What to expect

Tracy version	GPU zones shown
Unpatched	0
Patched (cuda-graph-gpu-zones.patch)	~30 (10 launches x 3 ops)

The graph structure

Each graph launch contains:

vector_add kernel (c = a + b)
Device-to-device memcpy
vector_add kernel (c = a + c)

The graph is launched 10 times, so 30 GPU operations total.