From 754d328c92d312c2f9f552c994611fa50ba93c5c Mon Sep 17 00:00:00 2001 From: Rafal Wojtczuk Date: Thu, 7 Apr 2011 14:44:18 +0000 Subject: [PATCH] GUIdocs changed --- GUIdocs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GUIdocs.md b/GUIdocs.md index 65151a03..8dbda8f0 100644 --- a/GUIdocs.md +++ b/GUIdocs.md @@ -37,7 +37,7 @@ Window content updates implementation Typical remote desktop applications, like *vnc*, pass the information on all changed window content in-band (say, over tcp). As the channel has limited throughput, this impacts video performance. In case of Qubes, *qubes\_gui* does not transfer all changed pixels via vchan. Instead, for each window, upon its creation or size change, *qubes\_gui* - asks *qubes\_drv* driver for the list of physical memory frames that hold the composition buffer of a window -- pass this information via {{{MFNDUMP}} message to *qubes\_guid* in dom0 +- pass this information via `MFNDUMP` message to *qubes\_guid* in dom0 Now, *qubes\_guid* has to tell dom0 Xorg server about the location of the buffer. There is no supported way (e.g. Xorg extension) to do this zero-copy style. The following method is used in Qubes: