Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 18 3月, 2013 1 次提交
  3. 19 12月, 2012 2 次提交
  5. 15 12月, 2012 1 次提交
  7. 01 11月, 2012 3 次提交
    • G
      pixman/vnc: remove dead code. · 94362682
      由 Gerd Hoffmann 提交于 
      Switching the vnc server framebuffer to use 32bpp unconditionally
turns the code bits which handle 8 and 16 bpp into dead code.
Remove them.
Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      94362682
    • G
      pixman/vnc: remove rgb_prepare_row* functions · 47683d66
      由 Gerd Hoffmann 提交于 
      Let pixman do it instead.
Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      47683d66
    • G
      pixman/vnc: use pixman images in vnc. · 9f64916d
      由 Gerd Hoffmann 提交于 
      The vnc code uses *three* DisplaySurfaces:

First is the surface of the actual QemuConsole, usually the guest
screen, but could also be a text console (monitor/serial reachable via
Ctrl-Alt-<nr> keys).  This is left as-is.

Second is the current server's view of the screen content.  The vnc code
uses this to figure which parts of the guest screen did _really_ change
to reduce the amount of updates sent to the vnc clients.  It is also
used as data source when sending out the updates to the clients.  This
surface gets replaced by a pixman image.  The format changes too,
instead of using the guest screen format we'll use fixed 32bit rgb
framebuffer and convert the pixels on the fly when comparing and
updating the server framebuffer.

Third surface carries the format expected by the vnc client.  That isn't
used to store image data.  This surface is switched to PixelFormat and a
boolean for bigendian byte order.
Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      9f64916d
  9. 21 8月, 2011 1 次提交
  11. 27 6月, 2011 2 次提交
  13. 10 4月, 2011 1 次提交
    • M
      vnc: tight: Fix crash after 2GB of output · 2caa9e9d
      由 Michael Tokarev 提交于 
      fix 2Gb integer overflow in in VNC tight and zlib encodings

As found by Roland Dreier <roland@purestorage.com> (excellent
catch!), when amount of VNC compressed data produced by zlib
and sent to client exceeds 2Gb, integer overflow occurs because
currently, we calculate amount of data produced at each step by
comparing saved total_out with new total_out, and total_out is
something which grows without bounds.  Compare it with previous
avail_out instead of total_out, and leave total_out alone.

The same code is used in vnc-enc-tight.c and vnc-enc-zlib.c,
so fix both cases.

There, there's no actual need to save previous_out value, since
capacity-offset (which is how that value is calculated) stays
the same so it can be recalculated again after call to deflate(),
but whole thing becomes less readable this way.
Reported-by: NRoland Dreier <roland@purestorage.com>
Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
Signed-off-by: NCorentin Chary <corentin.chary@gmail.com>
Signed-off-by: NAurelien Jarno <aurelien@aurel32.net>
      2caa9e9d
  15. 25 2月, 2011 1 次提交
  17. 24 2月, 2011 4 次提交
  19. 06 10月, 2010 1 次提交
  21. 04 9月, 2010 3 次提交
  23. 01 8月, 2010 2 次提交
  25. 28 7月, 2010 1 次提交
    • B
      Fix mingw32 build · 249cdb42
      由 Blue Swirl 提交于 
      Fix mingw32 build errors like
/src/qemu/ui/vnc-enc-tight.c: In function 'tight_detect_smooth_image24':
/src/qemu/ui/vnc-enc-tight.c:119: error: 'uint' undeclared (first use in this function)

Replace 'uint' with proper 'unsigned int'.
Signed-off-by: NBlue Swirl <blauwirbel@gmail.com>
      249cdb42
  27. 27 7月, 2010 15 次提交
  29. 14 6月, 2010 1 次提交
  31. 02 6月, 2010 1 次提交