capture-kernel-trace

Capture and analyze GPU kernel ATT traces using rocprofv3.

260|104|Updated Nov 23, 2025
One-click install
npx skills add https://github.com/ROCm/FlyDSL --skill capture-kernel-trace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capture-kernel-trace
Source: https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/capture-kernel-trace
Command: npx skills add https://github.com/ROCm/FlyDSL --skill capture-kernel-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture GPU kernel ATT traces from a GPU environment (local or remote Docker), configure input.yaml for the target kernel, execute rocprofv3 -i input.yaml with source mapping enabled, and download the latest ui_output_agent_* data for analysis.

Core Features & Use Cases

  • Kernel discovery: identify available kernels on the target GPU environment to determine the tracing targets.
  • Input configuration: generate and tailor input.yaml with kernel_include_regex and tracing parameters.
  • Trace collection: run rocprofv3 -i input.yaml to collect Advanced Thread Trace data with DWARF mapping when enabled.
  • Trace retrieval: fetch and organize the latest ui_output_agent_* directory and associated trace artifacts for inspection.

Quick Start

Run the capture-kernel-trace skill with your test script and an optional kernel pattern to start collecting ATT traces.

Frequently Asked Questions about capture-kernel-trace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture GPU kernel ATT traces using rocprofv3 in a remote environment?

To capture GPU kernel ATT traces remotely, you need SSH or Docker access to the target environment, rocprofv3 installed, and an input.yaml file configured with your kernel patterns to execute the tracing.

What is the process for discovering available kernels before collecting ATT traces?

Kernel discovery identifies available kernels on the target GPU environment to determine tracing targets, allowing you to generate a tailored input.yaml with specific kernel_include_regex and tracing parameters for rocprofv3.

How do I retrieve and organize ui_output_agent trace data after running rocprofv3?

After executing rocprofv3 -i input.yaml, retrieve the latest ui_output_agent_* directory and associated trace artifacts from the GPU environment, organizing them locally for post-analysis and inspection.

Do I need FLYDSL_DEBUG_ENABLE_DEBUG_INFO to get source mappings in ATT traces?

Yes, FLYDSL_DEBUG_ENABLE_DEBUG_INFO is required to enable DWARF source mappings in your ATT traces, ensuring that collected Advanced Thread Trace data includes accurate source-level mapping for analysis.

Can I use capture-kernel-trace for GPU profiling on local environments or is it remote only?

GPU kernel ATT trace collection works across both local and remote Docker environments, requiring rocprofv3 and proper input.yaml configuration to execute tracing and retrieve ui_output_agent_* data for analysis.

What are the limitations when collecting ATT traces with rocprofv3?

ATT trace collection with rocprofv3 requires proper remote access via SSH or Docker, FLYDSL_DEBUG_ENABLE_DEBUG_INFO for source mappings, and depends on accurate kernel discovery and input.yaml configuration for successful tracing.