PantheonSim / GPUs / AMD Radeon RX 7900 XTX

Simulated AMD Radeon RX 7900 XTX: a GPU profile for CUDA and ROCm testing

PantheonSim, the GPU simulator for CUDA and ROCm, simulates the AMD Radeon RX 7900 XTX (RDNA 3, gfx1100) as the profile amd/rx7900xtx. A Radeon RX 7900 XTX (Navi 31, 96 compute units), the first RDNA 3 part among the profiles. Its profile is built from public documents and not yet measured against a physical card.

The profile at a glance

These are the numbers a program can ask this simulated GPU, and the values rocm-smi and amd-smi show for it. They come from the profile file in the simulator's repository, pinned to one commit of it.

PropertyValue
Profile idamd/rx7900xtx
Vendor and architectureAMD, RDNA 3
GPU targetgfx1100
Device memory24.0 GiB, GDDR
Multiprocessors (as HIP reports them)48
Wavefront size32
Max threads per multiprocessor2048
Shared memory per block (opt-in maximum)64 KiB
L2 cache6 MiB
Power limit (profile)355 W
Maximum clocks (profile)2500 MHz shader, 2500 MHz memory
ECC memoryno
PCIe link reportedGen4 x16
Tensor or matrix coresyes
Verified (measured on a physical card)not yet measured

What this GPU is for

A Radeon RX 7900 XTX (Navi 31, 96 compute units), the first RDNA 3 part among the profiles.

RDNA 3 is the Radeon RX 7000 generation, gfx1100. Kernels run 32 lanes to a wave, as HIP builds them for it.

Among the 10 AMD profiles it ranks 6th by device memory (24.0 GiB) and 6th by multiprocessors as HIP counts them (48), counting the largest as first.

Is this profile verified?

No. This profile is marked not verified: it is built from public documents only, and nothing in it was measured on a physical card. Some figures are derived or copied from the nearest profile where the vendor publishes none, so treat them as approximate, and memory sizes as upper bounds. The profile file itself calls some of its values placeholders. Programs still run on it, and it still answers every call as the architecture's rules require, but a value such as a clock or a limit may differ from a real card's.

Simulate this GPU

Build the simulator (see the docs) or open the playground, then:

hipcc --offload-arch=gfx1100 my_app.hip -o my_app
vgpu run --gpu amd/rx7900xtx ./my_app
vgpu shell -y --gpu amd/rx7900xtx --count 4 --rocm 7.1.0
vgpu info --gpu amd/rx7900xtx

Build for this card's own gfx target, gfx1100. A program built for another target is refused by name, as the real runtime refuses it, and hipErrorNoBinaryForGpu means exactly this.

To use it every time, put gpu: amd/rx7900xtx in a pantheonsim.yaml settings file, or in a GitHub Actions job give the PantheonSim action gpu: amd/rx7900xtx (see CUDA and HIP tests in GitHub Actions). The simulator checks behaviour and has no timing model, so a run on a physical GPU before a release still counts. The ROCm and HIP guide explains the rest.

Where the numbers come from

Each profile file begins with a note on its sources. This is the note for AMD Radeon RX 7900 XTX, as written in the file:

Source note for amd/rx7900xtx

Values from public AMD documentation. verified: false means nothing here has been confirmed by hardware characterization yet, treat as placeholders. The first RDNA part here: gfx1100 (RDNA3, Navi 31), a consumer card whose kernels run 32 lanes to a wave, as HIP builds them for it. HIP counts its compute units in pairs (workgroup processors): 48 of the card's 96.

The GPU index lists every profile, and this one is not yet measured.

Other AMD profiles: