summaryrefslogtreecommitdiffstats
path: root/wiki/Graphics-Execution.md
diff options
context:
space:
mode:
Diffstat (limited to 'wiki/Graphics-Execution.md')
-rw-r--r--wiki/Graphics-Execution.md7
1 files changed, 0 insertions, 7 deletions
diff --git a/wiki/Graphics-Execution.md b/wiki/Graphics-Execution.md
index 7d67836..eea0574 100644
--- a/wiki/Graphics-Execution.md
+++ b/wiki/Graphics-Execution.md
@@ -25,12 +25,6 @@ render target is readable by the guest, and that image reaches the capture
path through the emulated mdev. The pixels must not come from another GPU, a
software rasteriser, or a host display round-trip.
-(The project has also published two deliberately-labelled two-VM demo videos
-that use the standard `virtio-gpu`/`virgl` virtual GPU on a host integrated
-GPU, and a CUDA-animation video that *does* run on the emulated vGPU through
-the compute path. The `virgl` videos are honest demonstrations of the guest
-experience; they are not this execution path, and their captions say so.)
-
## 2. The path a graphics command takes
```mermaid
@@ -232,7 +226,6 @@ requires it switched off, along with any external poke.
presented frame; the direct-GL CE ring still does not resolve.
* No frame-rate or latency numbers: the scheduled measurement is defined
(60 fps over 60 s, no forcing) but not yet met.
-* The `virgl`-based demo videos are a different, labelled path — not this one.
## 9. Related pages