changh95 commited on
Commit
d9bec5a
·
verified ·
1 Parent(s): 51354c1

Add Tenstorrent Blackhole tt-nn port

Browse files
Files changed (1) hide show
  1. SERVING.md +27 -0
SERVING.md CHANGED
@@ -63,6 +63,33 @@ fastapi / uvicorn / pydantic / pillow; `runtime.packages` adds to that set.
63
  Despite the name, this kind is not diffusion-only -- `jashansinghTT/s2-pro-blackhole` is a
64
  TTS model using it. It simply means "the model's own ASGI app under uvicorn".
65
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
66
  ## Known sharp edges (offline-validated, not yet hardware-validated)
67
 
68
  The manifest loads clean (`load_container_manifest(..., check_sources=False)` passes, which
 
63
  Despite the name, this kind is not diffusion-only -- `jashansinghTT/s2-pro-blackhole` is a
64
  TTS model using it. It simply means "the model's own ASGI app under uvicorn".
65
 
66
+ ## The catalog tags are automatic -- do not add them by hand
67
+
68
+ `tt-model-cache`, `tt-model-container` and `tt-model-catalog` are written by the real flow,
69
+ not by editing this card:
70
+
71
+ | tag | written by | source |
72
+ |---|---|---|
73
+ | `tt-model-cache` | `package` | `TT_MODEL_TAG` in `tt_kernel/__init__.py:9` |
74
+ | `tt-model-container` | `package` | `build.py:996` -- `{TT_MODEL_TAG, m.arch, m.kind, "tt-model-container"}` |
75
+ | `blackhole`, `tt-dit-server`, `p150` | `package` | same line, from `arch` / `kind` / each profile's `hardware` |
76
+ | `tt-model-catalog` | `--publish` | `cli.py:620` / `cli.py:820` |
77
+
78
+ So finishing step 5 produces exactly the tag set the catalog models carry. Adding them to
79
+ this repo now would be actively harmful, because **nothing validates them**:
80
+
81
+ - `tt-model-cache` is what `tt-model search` filters on (`hub.py:268`), so the repo would
82
+ show up as an installable bundle and `tt-model pull` would then fail -- there is no
83
+ `tt_kernel_manifest.json` here, only the authoring `tt-model.yaml`.
84
+ - `tt-model-container` asserts a v5.1 OCI image in `image/`, which does not exist yet.
85
+ - `tt-model-catalog` lists it in the public community index, which renders each entry by
86
+ reading `tt_kernel_manifest.json`.
87
+ - `tt-model publish <id>` does **not** check that the target is a real bundle -- it only
88
+ flips visibility and sets the tag -- so the guard rail you might expect is not there.
89
+
90
+ Until the bundle is built, the honest tag set is the one this card already carries
91
+ (`tenstorrent`, `blackhole`, `p150`, `ttnn`, `tt-metal`, plus the task tags).
92
+
93
  ## Known sharp edges (offline-validated, not yet hardware-validated)
94
 
95
  The manifest loads clean (`load_container_manifest(..., check_sources=False)` passes, which