Kohaku-TT

A native PyTorch device for Tenstorrent Blackhole cards (developed on P150A). tt is a torch.device like cuda: every aten op a model calls runs on the card as a TT-NN op, a composite of TT-NN ops or one of Kohaku-TT's own Metalium programs. Models, training loops and tools move to the card with .to(dev) and keep running op by op. It is for people who want to run and train ordinary PyTorch code on a Blackhole card, and for kernel authors who want their own Metalium programs as torch ops.

Status: early development. Eager execution, training and torch.compile run end to end on real models (ViT, Qwen2.5 training, the MOSS-Image text-to-image pipeline).

import torch
import kohakutt

dev = kohakutt.device(0)  # chip 0 as a torch.device ("tt:0")
x = torch.randn(4, 8, device=dev)
w = torch.randn(8, 3).to(dev)
y = torch.relu(x @ w + 1.0)  # queued on the card; returns at once
print(y.sum(dim=1).cpu())  # a host read waits for the result

Highlights

• Every Core ATen op runs on tt: 193 of 193 Core ATen overloads have a tt kernel or a composite of tt kernels (support table). An op without one raises KohakuTTUnsupportedOperator; the CPU runs it only when asked.
• A real device: storage-backed tensors with views and aliasing, an asynchronous default stream, autograd and optimizers on the card, torch.tt, torch.save / load.
• Trace capture and torch.compile: kohakutt.capture and the ktt_tt / ktt_tt_aot backends replay a step as one device trace.
• Own kernels where TT-NN falls short: flash attention (MHA / GQA / MQA, masks, causal, packed variable-length batches), layer / RMS norm with fp32 statistics, grouped and channels-last convolutions, fused transformer ops.
• Two cards as one device (experimental): kohakutt.mesh([0, 1]) shards tensors over a 1 x 2 mesh.
• Your kernels as torch ops, from Python, the Python kernel DSL or C++.
• Block-float weights (BFLOAT8_B / BFLOAT4_B), precision as a scope (kohakutt.numerics) and tools that report error against a float64 ruler.

• tinygrad: an early add-on registers the card as the tinygrad device "KTT".

One Blackhole P150A, bf16, eager, warm. The TT-NN column is the same model on TT-NN's kernels (KTT_CUSTOM_KERNELS=0); error is the median relative error against CPU float64 (CPU bf16 in brackets). MOSS-Image: bfp8 DiT weights, HiFi2, one chip.

Against tt-xla 1.4.0 on the same card (bf16; tt-xla compiled with its tt backend unless noted; a shared, loaded host, so compare within a row):

Every model tried, with errors, first-call times and the problems found: result zoo. Kernel-level results and their conditions: measured. The full feature list: features.

Install

A Blackhole card with its kernel driver and firmware. From PyPI (Linux x86-64, glibc 2.39 or newer, Python 3.13 or 3.14, PyTorch 2.10 to 2.15):

pip install --index-url https://download.pytorch.org/whl/cpu torch==2.15.0+cpu
pip install kohakutt          # --pre for the nightly builds
ktt sfpi                      # once: fetches the RISC-V kernel compiler into the cache
ktt doctor                    # read-only report of the host and every card

No tt-metal checkout is needed for the wheel. Building from a clone: install.

Usage

PyTorch: tensors, training, capture and compile

Model, loss and optimizer code is unchanged PyTorch; a repeated step can be captured once and replayed as one device trace (trace contract; examples/02_training.py, 03_trace.py, 04_compile.py):

import torch
import torch.nn.functional as F
from torch import nn

import kohakutt

dev = kohakutt.device(0)  # chip 0 as a torch.device ("tt:0")

# 1. Model, optimizer and data on the card: ordinary PyTorch.
model = nn.Sequential(
    nn.Linear(256, 512), nn.LayerNorm(512), nn.SiLU(), nn.Linear(512, 10)
).to(dev)
opt = torch.optim.AdamW(model.parameters(), lr=1e-3)
x = torch.randn(128, 256, device=dev)
y = torch.randint(0, 10, (128,)).to(dev)


def step(x, y):
    opt.zero_grad(set_to_none=False)  # a trace needs fixed gradient buffers
    loss = F.cross_entropy(model(x), y)
    loss.backward()
    opt.step()
    return loss.detach()


# 2. Eager: each op is queued on the card; .item() waits for the result.
for _ in range(3):
    print("eager loss", step(x, y).item())

# 3. Capture the step once, then replay it as one device trace.
replay = kohakutt.capture(step, x, y, warmup=3)
print("trace loss", replay(x, y).item())

# 4. Inference: precision is a scope; torch.compile takes a whole forward.
with torch.no_grad(), kohakutt.numerics(fidelity="HiFi4"):
    print("accuracy", (model(x).argmax(-1) == y).float().mean().item())
compiled = torch.compile(model, backend="ktt_tt")  # "ktt_tt_aot" for training

tinygrad (early add-on)

import kohakutt.tinygrad registers the card (chip 0) as the tinygrad device "KTT"; the code is plain tinygrad v0.14.0 (examples/tinygrad/01_tensors.py, 02_training.py):

from tinygrad import Context, Tensor, nn

import kohakutt.tinygrad  # noqa: F401  registers the device "KTT" (chip 0)


class Net:
    def __init__(self):
        self.hidden, self.out = nn.Linear(256, 512), nn.Linear(512, 4)

    def __call__(self, x):
        return self.out(self.hidden(x).silu())


# 1. Parameters and data on the card; the model code is plain tinygrad.
model = Net()
params = nn.state.get_parameters(model)
for p in params:
    p.to_("KTT")
opt = nn.optim.AdamW(params, lr=1e-3)
x = Tensor.randn(64, 256, device="KTT")
y = Tensor([0, 1, 2, 3] * 16, device="KTT")

# 2. Training steps run on the card; .item() waits for the result.
with Context(TRAINING=1):
    for _ in range(3):
        loss = model(x).sparse_categorical_crossentropy(y)
        opt.zero_grad()
        loss.backward()
        opt.step()
        print("loss", loss.item())

# 3. Inference, at a higher matmul fidelity for this scope.
with kohakutt.tinygrad.numerics(fidelity=3):
    print("accuracy", (model(x).argmax(axis=1) == y).mean().item())

The add-on is early and runs on one card. It shares the native bridge with the torch backend, so both frontends can run in one process on one open device.

• Precision: results match tinygrad's CPU backend up to the card's matmul precision; the fidelity scope narrows it (fused attention and the conv backward stay bf16).
• Comparing training runs: compare losses or gradients. Parameters after an Adam step differ by about lr wherever a gradient is near zero, on any backend.
• Random numbers: Tensor.rand / randn(..., device="KTT") and dropout are drawn on the card, reproducible under Tensor.manual_seed but not the CPU backend's stream; KTT_TINYGRAD_RAND=host gives that stream, drawn on the host.
• Dtypes: float32, bfloat16 and int32 run on the card. Kernels on float16, float64, other integers or stored bools run on the host, counted and warned once per dtype (KTT_TINYGRAD_DTYPES=error raises DtypeError instead); fp8 is not supported.
• Not supported yet: tinygrad's memory planner. torch must be installed.

More: docs/tinygrad.md, examples/tinygrad.

Two cards as one device (experimental)

kohakutt.mesh([0, 1]) opens two chips as one torch device. The mesh is experimental: it is built and tested as 1 x 2, and its API and defaults may change. Tensors of 1 MiB or more are sharded when created, smaller ones replicated, and the TT-NN collective an op needs is inserted for it. Marks set a module's own placement and return the same module (examples/05_mesh.py):

class Block(nn.Module):
    def __init__(self, d):
        super().__init__()
        self.norm = kohakutt.replicate(nn.LayerNorm(d))  # a copy on each chip
        self.up = kohakutt.colwise(nn.Linear(d, 4 * d))  # output features split
        self.down = kohakutt.rowwise(nn.Linear(4 * d, d))  # input features split

    def forward(self, x):
        return x + self.down(nn.functional.gelu(self.up(self.norm(x))))


mesh = kohakutt.mesh([0, 1])
model = nn.Sequential(Block(1024), Block(1024)).bfloat16().to(mesh)
with kohakutt.record_placements():
    out = model(torch.randn(512, 1024, dtype=torch.bfloat16).to(mesh))
print(kohakutt.placement(model[0].down.weight))  # "Sharded(dim=1)"
print(kohakutt.placement_log()[-1])  # op, inputs, output, conversions, reason
print(torch.tt.mesh_stats())  # collectives so far

kohakutt.shard(module, dim) marks a module's tensors sharded on dim, and kohakutt.place(module, weight="S(1)", bias="R") marks them one by one. Design and measurements: mesh.

Custom kernels

A Metalium program (reader, compute and writer kernels over circular buffers) becomes a torch op on tt tensors, run in order with every other op. In C++, the program builder and the op are built into an extension library (examples/kernels/cpp_extension):

// device side: swiglu_program.cpp builds the ProgramDescriptor for (a, b, out)
KTT_REGISTER_PROGRAM("kohakutt_example_cpp::swiglu", swiglu);

// torch side: swiglu_op.cpp
at::Tensor swiglu(const at::Tensor& a, const at::Tensor& b) {
    return ktt::extension::run(
        "kohakutt_example_cpp::swiglu", {a, b}, {{a.sizes().vec(), a.scalar_type()}}
    )[0];
}

kohakutt.extension.load("build/swiglu_ext/swiglu_ext.so") loads the library; the op is then torch.ops.kohakutt_example_cpp.swiglu(a_tt, b_tt).

With the kernel DSL (kohakutt.dsl.metal) the whole program is Python; the kernel sources are generated and checked against the hardware's rules, and sizes are runtime arguments, so a new shape or scale compiles nothing. The whole program and op for a * s + b, one tile per step (km is kohakutt.dsl.metal, kk is kohakutt.kernels, bits gives a float's fp32 bits; examples/kernels/dsl_metal/scaled_add_km.py):

@km.program("scaled_add")
def scaled_add_program(p, a: km.TensorRef, b: km.TensorRef, out: km.Out):
    start, count = p.split(p.runtime("tiles"))  # each core's range of tiles
    s = p.runtime("s")  # fp32 bits of the scale
    cb_a, cb_b, cb_out = p.cb(0, like=a), p.cb(1, like=b), p.cb(16, like=out)

    @p.dm0
    def reader(k):
        for i in k.range(count):
            a_slot, b_slot = cb_a.reserve(1), cb_b.reserve(1)
            k.read(a.page(start + i), a_slot)
            k.read(b.page(start + i), b_slot)
            k.reads_done()
            cb_a.push(1)
            cb_b.push(1)

    @p.compute(fp32_dest=True)
    def compute(c):
        c.startup(cb_a, cb_b, cb_out)
        for _ in c.range(count):
            cb_a.wait(1)
            cb_b.wait(1)
            with c.registers():
                c.init("copy", cb_a)
                c.copy(cb_a, 0, 0)  # a in register slot 0
                c.init("copy", cb_b)
                c.copy(cb_b, 0, 1)  # b in register slot 1
                c.init("mul_scalar")
                c.op("mul_scalar", 0, value=s)  # slot 0 = slot 0 * s
                c.init("add")
                c.op("add", 0, 1, 0)  # slot 0 = slot 0 + slot 1
                cb_out.reserve(1)
                c.pack(0, cb_out)
                cb_out.push(1)
            cb_a.pop(1)
            cb_b.pop(1)

    @p.dm1
    def writer(k):
        for i in k.range(count):
            cb_out.wait(1)
            k.write(cb_out, out.page(start + i))
            k.flushed()
            cb_out.pop(1)
        k.writes_done()


@km.op(
    "kohakutt_example::scaled_add_km(Tensor a, Tensor b, float s) -> Tensor",
    scaled_add_program,
)
def scaled_add(a, b, s):
    return km.Call(
        inputs={"a": a, "b": b},
        outputs={"out": (list(a.shape), a.dtype)},
        runtime={"tiles": kk.tile_count(a), "s": bits(s)},
    )

The tile level of the DSL (import kohakutt.dsl as kd, experimental) writes what one unit of work loads, computes and stores; cores, buffers, NoC calls and vector-unit code are derived, and the result is a metal-level program as above. SwiGLU, one tile per unit (examples/kernels/dsl_tile/ also has norms, rotary embeddings, softmax, linear layers with fused activations and a hand-written backward):

@kd.kernel
def swiglu(x: kd.Tensor, g: kd.Tensor, out: kd.Out):
    for t in kd.grid(kd.num_tiles(out)):
        a = kd.load(x.tiles[t])
        b = kd.load(g.tiles[t])
        kd.store(out.tiles[t], a * kd.sigmoid(a) * b)


y = swiglu(x_tt, g_tt)  # tt tensors in, a tt tensor out

Hand-written Metalium kernels from Python (kohakutt.kernels) and the full API: custom kernels, kernel DSL, tile level.

Limitations

• One device or mesh per process; the mesh is built and tested as 1 x 2. An op without a placed form gathers its input to both chips.
• On the mesh, a bf16 partial sum is rounded on each chip before the chips' sums are added, so ops on it carry a larger rounding error than on one card (mesh).
• A trace holds every intermediate of the captured graph; very large forwards do not fit as one trace.
• fp32 matmuls are accurate to about 1e-3 relative, not to CPU fp32.
• 1-D tensors are one padded tile row; bf16 NaN may come back as inf after device ops.
• Data movement (permutes, gathers of strided views) runs as TT-NN op chains, not near memory bandwidth; gather has its own kernel along the last dim only, and clamps out-of-range indices. Tensors whose last two dims are small pad to 32 x 32 tiles.
• Some attention calls (fp32, dropout) run PyTorch's math composite on tt ops.
• L1-resident activations are opt-in (KTT_L1_BUDGET); when they spill to DRAM, a view and its base that shared an L1 buffer no longer alias.
• The first call at a new shape of TT-NN's reshape, padded slice, permute and conv2d costs host setup (seconds at image sizes).

Details: limitations.

Documentation

Contributing

Open an issue first for a feature. Code conventions and the checks to run before a pull request are in development.

License

Apache-2.0.