#6629 [Docs] settings-register: 41 HIP knobs land without a status in 0.2.19 — the pristine tag fails tools/test_settings_register.py

open · @xyzzing · 0 コメント · GitHub で見る

Server & APIAMD / HIPNVIDIA / CUDADocumentation

本文


Hi — we maintain a small gfx1100 replay fork (xyzzing/Strata) and re-play it onto every upstream tag; the register-regen step in that routine is how this surfaced. Sharing in case having the full enumeration saves you the lookup.

### Problem and result

At the **v0.2.19 tag** (and on current main, `c6f6427d9`), `terminal/data/settings-register.json` carries **41 entries with `"status": ""`**, so on a pristine checkout:

```
$ python3 tools/test_settings_register.py
FAIL: test_every_entry_has_a_valid_status
    entries without a valid status: STRATA_DENSE_I8_TC, STRATA_DENSE_I8_TC_MIN_T,
    STRATA_DF2_ATTN_TC, ... (41 total, listed below)
```

(v0.2.17's register is clean, so this is new in the 0.2.19 cycle — all 41 names enter the file in the release commit `26350e438`.)

One small thing that might help prevent a recurrence: `terminal/data/settings-register.json` is in **docs.yml's** trigger paths (which runs `tools/check --only docs` — that check doesn't validate statuses) but not in **check.yml's** paths (which runs py-tools). So a commit touching only the register file skips the register test entirely, which is how a release-time register rewrite can land quietly. Adding the file to check.yml's paths would close that.

### The 41 names, with source-derived suggested statuses

Read out of each knob's unset/set behaviour in the code — only you know intent, so please treat this as a starting point, not a proposal:

- **default (10):** `STRATA_DENSE_I8_TC`, `STRATA_DENSE_I8_TC_MIN_T`, `STRATA_DFLASH_WMMA`, `STRATA_HC_Q8_BF16TC`, `STRATA_HC_Q8_TC`, `STRATA_HIPBLASLT`, `STRATA_HIPBLASLT_MIN_M`, `STRATA_HIP_MOE_I8`, `STRATA_PF_DENSE_FP4`, `STRATA_PREFILL_DENSE_I8_TC`
- **opt-in (19):** `STRATA_DF2_GEMM_TC`, `STRATA_GR_FUSED`, `STRATA_GR_RDNA`, `STRATA_HIPBLASLT_MOE_MIN_B`, `STRATA_HIP_FAST_DEC`, `STRATA_MEGAKERNEL`, `STRATA_NVFP4_DEC_SM120`, `STRATA_PF_MXFP8`, `STRATA_PF_MXFP8_CACHE_MIB`, `STRATA_PF_MXFP8_MIN_T`, `STRATA_PF_MXFP8_MOE`, `STRATA_PF_P1A_FL3`, `STRATA_PREFILL_ALWAYS_BORROW`, `STRATA_RDNA_KQ_ALL`, `STRATA_RDNA_Q6K`, `STRATA_ROUTE_TAIL_RENORM`, `STRATA_UMA_COHERENT`, `STRATA_VERIFY_DEVICE_HITS`, `STRATA_VHEAD_BITPLANE`
- **rollback (8):** `STRATA_DF2_ATTN_TC`, `STRATA_DF2_CTX_BATCH`, `STRATA_GFX11_CHUNK`, `STRATA_GFX11_DEFAULTS`, `STRATA_GFX11_WMMA_DEFAULTS`, `STRATA_HIP_MAPPED_COHERENT`, `STRATA_PF_P1A_PLAIN`, `STRATA_RDNA_Q80_WMMA`
- **research (4):** `STRATA_GFX11_EXP8`, `STRATA_HIP_DSPARK_PROF`, `STRATA_HIP_PROF`, `STRATA_HIP_TREE_PROF`

Two that single-status labels fit awkwardly, in case it helps: `STRATA_HC_Q8_TC` / `STRATA_HC_Q8_BF16TC` return 0 under `__HIPCC__` (a default on CUDA, inert on HIP builds), and `STRATA_VERIFY_DEVICE_HITS` is engine-default `=1` on sm_86/gfx12/sm_121 but opt-in on discrete gfx11 per the wording of your own `c8c82e300` — the note field can carry the arch split either way.

### Validation

- Pristine v0.2.19 in a throwaway worktree: `python3 tools/test_settings_register.py` → FAILED (only `test_every_entry_has_a_valid_status`; the other 7 pass).
- With the table above applied as statuses + file:line evidence notes: 8/8 register tests, `tools/check --only docs` 6/6.
- If the table is useful as-is, happy to send it as a PR instead — whichever is less work for you.

### Related discussion (heads-up, entirely non-urgent and possibly already known)

The same register test is currently failing in the CI `py-tools` step on main — run **45016591569** (tip commit) shows it on all three OSes. That run also has unrelated failures (`test_setup_model_pins`, `test_setup_mac`, `test_strata_mcp`, host typecheck/build, `Python terminal/serve/`) — mentioning them only so the register item doesn't get mistaken for that cluster; the two look independent.

### Limits

Statuses are source-derived from the read sites, not measured; gfx1100/HIP perspective (the CUDA-only entries were classified from code, not run). Full per-entry notes with file:line live in our fork's register if useful.

*Prepared with AI assistance (fork-maintenance agent); reviewed and posted by the operator.*

関連リンク

インストール・モデル・リリースへのサイト内リンク。