summaryrefslogtreecommitdiffstats
path: root/docs/03-architecture/02-guest-stack-and-cudasw.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/03-architecture/02-guest-stack-and-cudasw.md')
-rw-r--r--docs/03-architecture/02-guest-stack-and-cudasw.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/docs/03-architecture/02-guest-stack-and-cudasw.md b/docs/03-architecture/02-guest-stack-and-cudasw.md
index f9fe249..845e00f 100644
--- a/docs/03-architecture/02-guest-stack-and-cudasw.md
+++ b/docs/03-architecture/02-guest-stack-and-cudasw.md
@@ -95,8 +95,10 @@ module-owned GPU running its real GSP firmware as the resource-manager server
(see
[`../../userspace/cuda/docs/08-virtualization-approaches.md`](../../userspace/cuda/docs/08-virtualization-approaches.md)
and [`08-physical-gpu-integration.md`](08-physical-gpu-integration.md)) — with
-CE-class copies forwarded to the physical copy engine (default off) and GR
-kernel execution blocked on GR engine-context validity.
+CE-class copies forwarded to the physical copy engine (default off); 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)).
For the CUDA userspace side of this stack — its architecture, how it is built
and executes, and the exact kernel/GPU interface contract we must satisfy —