Skip to content

Radeon AI PRO R9700 (gfx1201, RDNA4) support #1781

Closed

Description

@mehdi-saeedi

Tracking issue for running Hyperloom on the AMD Radeon AI PRO R9700 (gfx1201, RDNA4): a single node, vLLM through Magpie's gfx12 runner, with GEAK and forge as kernel agents.

Scope

  • Single node, single GPU (the configuration validated so far).
  • vLLM only. Other frameworks have no validated gfx12 runner and are rejected at launch.
  • Out of scope for now: multi-node, bare metal, the targeted-build (compiled / AITER) path, and a bare gfx1201 without the R9700 product name (it stays product-unknown).

Component bring-up (merged)

Hyperloom

Fixes found during bring-up (generic, not RDNA-specific)

GEAK fixes found during bring-up

Activity

  1. mehdi-saeedi commented on Oct 8, 2026

    @mehdi-saeedi
    CollaboratorAuthor

    Review round addressed. @chaojhou reviewed every Hyperloom PR here; all of the must-fix items are now pushed, and the PR descriptions were updated where the behaviour changed.

    The MAGPIE_REF bump stays a separate follow-up, opened once this round settles: it moves Magpie for every board, while #1782 is additive for all of them, so the two carry different risk.

  2. chaojhou commented on Oct 22, 2026

    @chaojhou
    Collaborator

    Every item in this tracking issue has landed on main:

    Closing as resolved. The older open RDNA4 PRs (#1296, #1757, #1032) were not part of this checklist and are triaged separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    awaiting-author-responseWaiting for issue author to reply (auto-managed)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions