Run any Skill in Manus with one click

cosim-gpu-rocm-stack

Stars1

Forks1

UpdatedJuly 7, 2026 at 08:51

Read before debugging guest-side ROCm behavior such as HSA signals, HIP waits, KFD ioctls, driver parameters, PASID/VMID routing, or known cosim runtime quirks.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

gevico

gevico/cosim-gpu-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	cosim-gpu-rocm-stack
description	Read before debugging guest-side ROCm behavior such as HSA signals, HIP waits, KFD ioctls, driver parameters, PASID/VMID routing, or known cosim runtime quirks.

Cosim ROCm Stack

Use this as the guest-side ROCm routing guide. It explains when a symptom belongs to test policy, guest inspection, debug evidence, or model-side review. Detailed runtime semantics live in references/rocm-runtime-reference.md; read that file when debugging HSA signals, HIP API waits, KFD ioctls, PASID, VMID, or driver parameters.

Stack Overview

HIP API
  -> ROCclr
    -> ROCr / HSA runtime
      -> amdgpu KFD
        -> amdgpu DRM
          -> gem5 GPU model through QEMU

Routing

Question	First route
Environment defaults or `HSA_ENABLE_INTERRUPT`	`cosim-gpu-test`, then `scripts/cosim_guest_env.sh`
Guest device visibility, driver load, debugfs	`cosim-gpu-guest`
Non-PASS row, hang, crash, or timeout	`cosim-gpu-debug`
Disk image package or service changes	`cosim-gpu-disk-image-edit`
HSA signal, HIP wait, KFD ioctl, PASID or VMID meaning	`references/rocm-runtime-reference.md`

Evidence To Collect

Use cosim-gpu-guest and cosim-gpu-debug to collect:

amdgpu and KFD kernel log excerpts
PCI device state and loaded kernel modules
ROCm agent and memory visibility
KFD debugfs state when signal or queue progress is suspected
program identity, interrupt mode, verdict, matrix row, and artifact path

When runtime symbols or debug builds are needed, use repository scripts and cosim-gpu-disk-image-edit; do not embed package-install procedures in this skill.

More from this repository

same repository

cosim-gpu-debug

gevico/cosim-gpu-skills

Use as the main entry for cosim debugging: gem5 crashes, assertions, hangs, timeouts, address translation faults, non-PASS test results, guest-side waits, and QEMU exits that may be secondary to gem5. Collect logs, preserve live state when needed, route to gem5 model references, and decide the first failing component.

2026-07-141

cosim-gpu-build

gevico/cosim-gpu-skills

Use when building gem5 or QEMU, checking build provenance, or preserving gem5 incremental builds across worktrees. Delegates to scripts/cosim_build.sh; never hand-roll Docker, scons, or QEMU make commands.

2026-07-071

cosim-gpu-codex-review

gevico/cosim-gpu-skills

Use when delegating independent code review, design review, or focused bug investigation to an AI reviewer. Provides delegation templates and records reviewer evidence; higher-level review flow remains in cosim-gpu-review or cosim-gpu-rlcr-loop.

2026-07-071

cosim-gpu-disk-image-edit

gevico/cosim-gpu-skills

Use when the guest disk image needs modification without a full rebuild. Mount with guestmount, add files, systemd services, kernel module config.

2026-07-071

cosim-gpu-flow-plan

gevico/cosim-gpu-skills

Use as the first step for non-trivial cosim testing, debugging, review, or iterative implementation tasks. Do not use for ordinary repository maintenance such as commit splitting, submodule pointer updates, author config, or documentation-only cleanup.

2026-07-071

cosim-gpu-guest

gevico/cosim-gpu-skills

Use when you need to send commands to a running cosim guest. Console pipe interaction, 9p share mount, GPU status check, manual driver load.

2026-07-071

name	cosim-gpu-rocm-stack
description	Read before debugging guest-side ROCm behavior such as HSA signals, HIP waits, KFD ioctls, driver parameters, PASID/VMID routing, or known cosim runtime quirks.

Cosim ROCm Stack

Stack Overview

HIP API
  -> ROCclr
    -> ROCr / HSA runtime
      -> amdgpu KFD
        -> amdgpu DRM
          -> gem5 GPU model through QEMU

Routing

Question	First route
Environment defaults or `HSA_ENABLE_INTERRUPT`	`cosim-gpu-test`, then `scripts/cosim_guest_env.sh`
Guest device visibility, driver load, debugfs	`cosim-gpu-guest`
Non-PASS row, hang, crash, or timeout	`cosim-gpu-debug`
Disk image package or service changes	`cosim-gpu-disk-image-edit`
HSA signal, HIP wait, KFD ioctl, PASID or VMID meaning	`references/rocm-runtime-reference.md`

Evidence To Collect

Use cosim-gpu-guest and cosim-gpu-debug to collect:

amdgpu and KFD kernel log excerpts
PCI device state and loaded kernel modules
ROCm agent and memory visibility
KFD debugfs state when signal or queue progress is suspected
program identity, interrupt mode, verdict, matrix row, and artifact path

When runtime symbols or debug builds are needed, use repository scripts and cosim-gpu-disk-image-edit; do not embed package-install procedures in this skill.