diff options
Diffstat (limited to 'docs/04-implementation/02-practical-challenges-and-adversarial-interop.md')
| -rw-r--r-- | docs/04-implementation/02-practical-challenges-and-adversarial-interop.md | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/docs/04-implementation/02-practical-challenges-and-adversarial-interop.md b/docs/04-implementation/02-practical-challenges-and-adversarial-interop.md index 4b886b3..93245c4 100644 --- a/docs/04-implementation/02-practical-challenges-and-adversarial-interop.md +++ b/docs/04-implementation/02-practical-challenges-and-adversarial-interop.md @@ -56,8 +56,11 @@ without a methodology is not accepted in this project. physical GPU (see §3). CE-class copies and their semaphore releases are now forwarded to the physical copy engine (default off) with a host-side fault relay, and memsets/copies/releases the host decoder understands still run in - software as a fail-closed correctness bridge. No CUDA kernel is forwarded - yet: GR kernel execution is blocked on GR engine-context validity. + software as a fail-closed correctness bridge. GR (kernel) execution is the + open frontier: a forwarded guest launch reaches the front-end but the inline + launch-descriptor install has not been observed and no grid has dispatched + (context validity at dispatch is ruled out — see + [`03-execution-frontier.md`](03-execution-frontier.md)). ## 3. Forwarding: the options and the chosen mechanism |