Kernel Trace Analysis

Profile and analyze GPU kernel ATT traces to identify stall hotspots and produce an optimization plan.

All analysis is done by running the bundled hotspot_analyzer.py (ATT) and pmc_l2_analyzer.py (PMC CSVs); never recompute their metrics yourself. Do not use GUI tools.

If the question is only "did my change increase register pressure, spills, or LDS?", use /isa-resource-diff first — it is compile-only, needs no GPU or profiler run, and answers in seconds. Come here when you need to know why a kernel is slow rather than what resources it uses.

To pick an LLVM knob that changes what the compiler emits — a compile hint, a function attribute, an -mllvm flag — and to prove it took effect, use /llvm. That is also compile-only.

Arguments