From f89fcb14ccdf9e8faf07ac42970c98f3ba7959f2 Mon Sep 17 00:00:00 2001 From: Arthur Hanson Rasmusson Date: Thu, 1 Oct 2026 00:06:19 -0400 Subject: docs: refresh status wording after the 64/64 baseline and the physical-backend lock --- userspace/cuda/READ-ME-FIRST.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) (limited to 'userspace') diff --git a/userspace/cuda/READ-ME-FIRST.md b/userspace/cuda/READ-ME-FIRST.md index 9adcf75..8d912dd 100644 --- a/userspace/cuda/READ-ME-FIRST.md +++ b/userspace/cuda/READ-ME-FIRST.md @@ -30,9 +30,13 @@ tooling. **echo the request's params**, because the driver copies 16 bytes of class params back over the caller's 8-byte local (the hook's saved `rbp`) — a zeroed reply is what made `rbp=0` (§3.5). The engine inventory is now - complete (the async copy engine is included); context creation reaches a - completion wait that currently ends in `rc=999` (§3.6 carries the - historical analysis and a status note). §3.3 gives the engine-record layout + complete (the async copy engine is included); context creation now returns + and the whole driver-API smoke test completes `ALL OK`, with the 64-byte + payload round-tripping exactly (64/64, re-verified on the current build). + The frontier is real execution on the physical GPU — the runtime client + initializes and queues a kernel launch, but execution awaits the backend. + §3.6 carries the historical analysis of the topology blocker. §3.3 gives the + engine-record layout (`base+0x2fec`, `+0x300c+(idx-1)*0x14`, `+0x350c`, `+0x351c+(idx-0x16)*0x14`; fields +0/+8/+0xc) and §3.7 lists exactly what the emulation should check first. -- cgit v1.2.3