1. 27 9月, 2018 1 次提交
    • G
      qxl: use guest_monitor_config for local renderer. · 979f7ef8
      Gerd Hoffmann 提交于
      When processing monitor config from guest store head0 width and height
      for single-head configurations.  Use these when creating the
      DisplaySurface in the local renderer.
      
      This fixes a rendering issue with wayland.  Wayland rounds up the
      framebuffer width and height to a multiple of 64, so with odd
      resolutions (800x600 for example) the framebuffer is larger than the
      actual screen.  The monitor config has the actual screen size though.
      
      This fixes guest display for anything using the local renderer
      (non-spice UI, screendump monitor command).
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      Reviewed-by: NMarc-André Lureau <marcandre.lureau@redhat.com>
      Message-id: 20180919103057.9666-1-kraxel@redhat.com
      979f7ef8
  2. 21 8月, 2018 1 次提交
  3. 22 1月, 2018 1 次提交
  4. 18 12月, 2017 1 次提交
  5. 24 4月, 2017 1 次提交
    • G
      qxl: add xres and yres properties · 6f663d7b
      Gerd Hoffmann 提交于
      Add properties for the default display resolution, pass
      on that information to the guest so the driver can use it.
      
      Also move up qxl_crc32() function so we don't need a
      forward declaration.
      
      Additionally guest driver updates are needed so the
      guest driver will actually pick this up, which will
      probably land in linux kernel 4.12.
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      Message-id: 20170421092234.8368-1-kraxel@redhat.com
      6f663d7b
  6. 11 4月, 2017 1 次提交
  7. 12 7月, 2016 1 次提交
  8. 06 7月, 2016 2 次提交
  9. 16 7月, 2015 1 次提交
  10. 19 5月, 2015 1 次提交
  11. 06 5月, 2014 1 次提交
    • K
      PortioList: Store PortioList in device state · 848696bf
      Kirill Batuzov 提交于
      PortioList is an abstraction used for construction of MemoryRegionPortioList
      from MemoryRegionPortio. It can be used later to unmap created memory regions.
      It also requires proper cleanup because some of the memory inside is allocated
      dynamically.
      
      By moving PortioList ot device state we make it possible to cleanup later and
      avoid leaking memory.
      
      This change spans several target platforms.  The following testcases cover all
      changed lines:
        qemu-system-ppc -M prep
        qemu-system-i386 -vga qxl
        qemu-system-i386 -M isapc -soundhw adlib -device ib700,id=watchdog0,bus=isa.0
      Signed-off-by: NKirill Batuzov <batuzovk@ispras.ru>
      Reviewed-by: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NAndreas Färber <afaerber@suse.de>
      848696bf
  12. 04 11月, 2013 1 次提交
  13. 18 9月, 2013 1 次提交
  14. 09 4月, 2013 1 次提交
  15. 01 3月, 2013 1 次提交
    • P
      hw: include hw header files with full paths · 83c9f4ca
      Paolo Bonzini 提交于
      Done with this script:
      
      cd hw
      for i in `find . -name '*.h' | sed 's/^..//'`; do
        echo '\,^#.*include.*["<]'$i'[">], s,'$i',hw/&,'
      done | sed -i -f - `find . -type f`
      
      This is so that paths remain valid as files are moved.
      
      Instead, files in hw/dataplane are referenced with the relative path.
      We know they are not going to move to include/, and they are the only
      include files that are in subdirectories _and_ move.
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      83c9f4ca
  16. 19 12月, 2012 3 次提交
  17. 17 12月, 2012 1 次提交
  18. 08 10月, 2012 1 次提交
  19. 05 9月, 2012 2 次提交
  20. 22 6月, 2012 3 次提交
  21. 03 5月, 2012 1 次提交
  22. 20 4月, 2012 1 次提交
  23. 29 2月, 2012 1 次提交
    • G
      qxl: add optinal 64bit vram bar · 6f2b175a
      Gerd Hoffmann 提交于
      This patch adds an 64bit pci bar for vram.  It is turned off by default.
      It can be enabled by setting the size of the 64bit bar to be larger than
      the 32bit bar.  Both 32bit and 64bit bar refer to the same memory.  Only
      the first part of the memory is available via 32bit bar.
      
      The intention is to allow large vram sizes for 64bit guests, by allowing
      the vram bar being mapped above 4G, so we don't have to squeeze it into
      the pci I/O window below 4G.
      
      With vram_size_mb=16 and vram64_size_mb=256 it looks like this:
      
      00:02.0 VGA compatible controller: Red Hat, Inc. Device 0100 (rev 02) (prog-if 00 [VGA controller])
              Subsystem: Red Hat, Inc Device 1100
              Physical Slot: 2
              Flags: fast devsel, IRQ 10
              Memory at f8000000 (32-bit, non-prefetchable) [size=64M]
              Memory at fc000000 (32-bit, non-prefetchable) [size=16M]
              Memory at fd020000 (32-bit, non-prefetchable) [size=8K]
              I/O ports at c5a0 [size=32]
              Memory at ffe0000000 (64-bit, prefetchable) [size=256M]
              Expansion ROM at fd000000 [disabled] [size=64K]
      
      [ mapping above 4G needs patched seabios:
        http://www.kraxel.org/cgit/seabios/commit/?h=pci64 ]
      6f2b175a
  24. 27 2月, 2012 5 次提交
  25. 21 2月, 2012 1 次提交
  26. 01 11月, 2011 1 次提交
    • G
      qxl: stride fixup · 0e2487bd
      Gerd Hoffmann 提交于
      spice uses negative stride value to signal the bitmap is upside down.
      The qxl renderer (used for scl, vnc and screenshots) wants a positive
      value because it is easier to work with.  The positive value is then
      stored in the very same variable, which has the drawback that the
      upside-down test works only once.  Fix by using two variables.
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      0e2487bd
  27. 25 10月, 2011 1 次提交
  28. 08 8月, 2011 1 次提交
  29. 03 8月, 2011 2 次提交
    • G
      qxl: bump pci rev · 9197a7c8
      Gerd Hoffmann 提交于
      Inform guest drivers about the new features I/O commands we have
      now (async commands, S3 support) if building with newer spice, i.e.
      if SPICE_INTERFACE_QXL_MINOR >= 1.
      
      sneaked in some 81+ column line spliting.
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      Signed-off-by: NAlon Levy <alevy@redhat.com>
      9197a7c8
    • A
      qxl: async io support using new spice api · 5ff4e36c
      Alon Levy 提交于
      Some of the QXL port i/o commands are waiting for the spice server to
      complete certain actions.  Add async versions for these commands, so we
      don't block the vcpu while the spice server processses the command.
      Instead the qxl device will raise an IRQ when done.
      
      The async command processing relies on an added QXLInterface::async_complete
      and added QXLWorker::*_async additions, in spice server qxl >= 3.1
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      Signed-off-by: NAlon Levy     <alevy@redhat.com>
      5ff4e36c