summaryrefslogtreecommitdiffstats
path: root/userspace/cuda/570.144
diff options
context:
space:
mode:
Diffstat (limited to 'userspace/cuda/570.144')
-rw-r--r--userspace/cuda/570.144/docs/ANALYSIS-cuctxcreate-segv.md7
1 files changed, 4 insertions, 3 deletions
diff --git a/userspace/cuda/570.144/docs/ANALYSIS-cuctxcreate-segv.md b/userspace/cuda/570.144/docs/ANALYSIS-cuctxcreate-segv.md
index db38802..666a4e2 100644
--- a/userspace/cuda/570.144/docs/ANALYSIS-cuctxcreate-segv.md
+++ b/userspace/cuda/570.144/docs/ANALYSIS-cuctxcreate-segv.md
@@ -3,8 +3,9 @@
> **Status: historical (2026-09-23 PART 9).** The segfault described here was
> fixed in PART 10 (the RM allocation reply now echoes the request parameters,
> which prevents a 16-byte class-params copy-back from zeroing the caller's
-> saved frame pointer). The current blocker is the missing async copy engine in
-> the emulated engine list (`cuCtxCreate` returns `999`). For the corrected,
+> saved frame pointer). The engine-topology blocker that followed was also
+> since resolved (the async copy engine is included); the current frontier is
+> the completion/execution path. For the corrected,
> current analysis see
> [`../../docs/05-570.144-decompilation.md`](../../docs/05-570.144-decompilation.md)
> and [`../../READ-ME-FIRST.md`](../../READ-ME-FIRST.md). The runtime
@@ -22,7 +23,7 @@ First analysis note for the CUDA userspace driver under Open-IOV. Companion to
|---|---|
| `cuInit(0)` | **OK** (previous sessions: failed) |
| `cuDeviceGetCount` / `cuDeviceGet` | **OK** (device 0) |
-| `cuCtxCreate` | **SIGSEGV inside libcuda** - the current blocker |
+| `cuCtxCreate` | **SIGSEGV inside libcuda** - the blocker at this snapshot (since fixed) |
| `cuMemAlloc` / copies / `ALL OK` | not reached yet |
Guest: Ubuntu 24.04, driver **570.144** (open kernel modules + libcuda