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 | 8 |
1 files changed, 5 insertions, 3 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 3265f47..4b886b3 100644 --- a/docs/04-implementation/02-practical-challenges-and-adversarial-interop.md +++ b/docs/04-implementation/02-practical-challenges-and-adversarial-interop.md @@ -53,9 +53,11 @@ without a methodology is not accepted in this project. are answered from cached/derived state where the hardware has no side effects the guest can observe. * **Real work** (grid launches, copies) is meant to be forwarded to the - physical GPU (see §3). Today only the work the host decoder understands — - memsets, copies and semaphore releases — is executed in software as a - correctness bridge; no CUDA kernel is forwarded yet. + 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. ## 3. Forwarding: the options and the chosen mechanism |