Skip to content

Add experimental Radeon 8065S (Halo/gfx1151) custom-workload support - #1468

Draft
powderluv wants to merge 1 commit into
AMD-AGI:mainfrom
powderluv:feat/halo-gfx1151
Draft

Add experimental Radeon 8065S (Halo/gfx1151) custom-workload support#1468
powderluv wants to merge 1 commit into
AMD-AGI:mainfrom
powderluv:feat/halo-gfx1151

Conversation

@powderluv

Copy link
Copy Markdown

Radeon 8065S currently has no dispatch identity, and spaced product names such as AMD Radeon 8065S are not recognized. This adds experimental Halo custom-workload bring-up: radeon8065s resolves to gfx1151 / 40 CUs, keeps its own script runner label, and is recognized through rocm-smi or PyTorch product names. Generic AMD Radeon Graphics on gfx1151 remains ambiguous and requires an explicit board selection.

The change includes a standalone GPU attention smoke workload checked against an independent CPU reference, plus setup and validation limits. It does not add Instinct peak constants, serving runners, scheduler changes, provider changes, or dependency workarounds.

Closes #1467. Related platform work: #1390 adds broader Radeon 8060S support. This smaller PR covers the separately tested Radeon 8065S identity and ambiguous-name handling. External Magpie/GEAK/TraceLens bring-up remains outside this contribution; no full kernel-optimization support is claimed.

Validation:

  • 49 focused GPU identity, provenance, and fusion architecture tests passed.
  • ruff check . and ruff format --check . passed.
  • Hardware smoke passed on gfx1151 with AMD PyTorch 2.13.0+rocm10.0.0; maximum absolute error 0.000443 against CPU FP32.
  • Mypy passed for the three modified production modules with --python-version 3.14. Default repository-wide mypy stops in installed NumPy stubs because the configured Python target is older than their syntax.
  • Full pytest (excluding the repository’s three E2E markers): 20,517 passed, 72 failed, 33 skipped, 77 deselected, 8 xfailed. Rechecking the 72 failures with inherited credentials removed: 64 passed, 8 failed. Those same 8 failures reproduce against unchanged main (e3a0ef325) in this environment; they concern source-resolver paths, Python 3.14 behavior, and campaign/shadow-repo handling. The full suite is not claimed green.

Physical end-to-end evidence is limited to the local custom Qwen3-0.6B BF16 benchmark: baseline approximately 67 tokens/s, configuration candidates exercised, no accepted gain. The 15-minute source/kernel trial exhausted its budget before GEAK executed.

Breaking changes: no. Single concern: initial Radeon 8065S platform identification and a reproducible custom-workload smoke test.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Track experimental Radeon 8065S (Halo/gfx1151) custom-workload bring-up

1 participant