diff options
Diffstat (limited to 'docs/03-architecture/03-gsp-and-gsp-rm.md')
| -rw-r--r-- | docs/03-architecture/03-gsp-and-gsp-rm.md | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/docs/03-architecture/03-gsp-and-gsp-rm.md b/docs/03-architecture/03-gsp-and-gsp-rm.md index 10e6a73..56e77be 100644 --- a/docs/03-architecture/03-gsp-and-gsp-rm.md +++ b/docs/03-architecture/03-gsp-and-gsp-rm.md @@ -232,9 +232,11 @@ The engine-inventory row was the CUDA blocker at the time of writing: `libcuda` filters the engine list it receives against the class list and expects the async copy engine to be present, because the secondary (async) engine record is otherwise zeroed. That inventory is now complete and context -creation passes; the current frontier is engine execution, where CE-class -copies are forwarded to the physical copy engine (default off) and GR kernel -execution is blocked on GR engine-context validity. See +creation passes; the current frontier is engine execution: CE-class copies are +forwarded to the physical copy engine (default off), and for GR a forwarded +guest launch reaches the front-end but the inline launch-descriptor install has +not been observed (context validity at dispatch is ruled out; see +[`../04-implementation/03-execution-frontier.md`](../04-implementation/03-execution-frontier.md)). See [`../../userspace/cuda/docs/05-570.144-decompilation.md`](../../userspace/cuda/docs/05-570.144-decompilation.md) section 3.7 for the offsets and the consumed fields, and [`../../userspace/cuda/docs/03-driver-and-gpu-interface.md`](../../userspace/cuda/docs/03-driver-and-gpu-interface.md) |