1. 06 Apr, 2016 1 commit
    • Christophe Fergeau's avatar
      xspice: Don't create Xorg time in timer_add · edd1a409
      Christophe Fergeau authored
      SpiceCoreInterface::timer_add() is used by spice-server for integration
      with external mainloops. timer_add() is only meant to create a disabled
      timer, this timer will then be started with a call to timer_start().
      
      The current implementation in Xspice creates a timer which will trigger
      in a very long time, assuming this will never happen. This 'forever' is
      1,000,000 seconds, which amounts to 11 days. After that time, some
      timers which are meant to be disabled (eg migration related timers in
      spice-server) fire, then causing a crash with some failed assertions.
      
      Instead of creating the X timer right away in timer_add(), we can wait
      until timer_start() is called before starting it, which avoids this
      issue.
      edd1a409
  2. 24 Mar, 2016 5 commits
  3. 11 Jan, 2016 1 commit
  4. 11 Dec, 2015 2 commits
  5. 16 Nov, 2015 2 commits
  6. 09 Nov, 2015 2 commits
  7. 03 Nov, 2015 1 commit
  8. 02 Nov, 2015 1 commit
  9. 26 Oct, 2015 4 commits
  10. 19 Oct, 2015 1 commit
  11. 09 Sep, 2015 1 commit
  12. 07 Sep, 2015 3 commits
  13. 18 Aug, 2015 1 commit
    • Uri Lublin's avatar
      uxa: fix compiler warnings (initialize width, height, [xy]Dst_copy) · 2f4a2fe2
      Uri Lublin authored
      Some compiler warnings for example:
      uxa-glyphs.c:1045: warning: ‘width’ may be used uninitialized in this function
      uxa-glyphs.c:1045: warning: ‘height’ may be used uninitialized in this function
      uxa-render.c:1090: warning: ‘xDst_copy’ may be used uninitialized in this function
      uxa-render.c:1090: warning: ‘yDst_copy’ may be used uninitialized in this function
      
      I think these can never actually happen as the code protects use of
      those uninitialized variables, but I'd not "argue" with the compiler.
      2f4a2fe2
  14. 10 Aug, 2015 3 commits
  15. 04 Aug, 2015 2 commits
    • Christophe Fergeau's avatar
      Fix compilation with newer Xorg versions · a184774a
      Christophe Fergeau authored
      Xorg 1.18 stopped exporting some xfont related symbols in its
      headers/shared libraries, which causes QXL to fail to build:
      
      uxa-damage.c:947:5: error: implicit declaration of function 'QueryGlyphExtents' [-Werror=implicit-function-declaration]
           QueryGlyphExtents(font, charinfo, n, &extents);
      
      The missing definition can be found in xfont, so this commit addes the
      needed configure.ac checks and includes.
      Note that dixfontstr.h must be included before the xfont headers or this
      will cause compile-time warnings on older Xorg versions (eg 1.17)
      a184774a
    • Christophe Fergeau's avatar
      Use <> for system-includes · 83e00bb5
      Christophe Fergeau authored
      These headers come from /usr/include/xorg/ so it's clearer if they are
      included using <>. While at it, I've reordered them alphabetically.
      83e00bb5
  16. 22 Jun, 2015 1 commit
    • Javier Celaya's avatar
      Fix drawable mm_time with KMS · e765cc5e
      Javier Celaya authored
      When KMS is enabled, the mm_time value of a QXLDrawable is undefined.
      This results in severe synchronization problems. This patch sets it to
      zero to force the spice-server to use the local clock.
      e765cc5e
  17. 01 Jun, 2015 1 commit
    • Jeremy White's avatar
      Do not process watches on select() error. · d99213d4
      Jeremy White authored
      This enables a kill of an Xorg process to propagate further.
      Without this, the read masks would be set, and we could end up
      blocking in an accept() call and not exiting from the signal.
      d99213d4
  18. 22 May, 2015 2 commits
  19. 30 Apr, 2015 1 commit
    • Adam Jackson's avatar
      Use pci_io_write8 instead of outb · c1e88427
      Adam Jackson authored
      This ensures better portability as some arches (eg aarch64) don't have
      outb.
      On linux pci_io_* try to open the sysfs map file corresponding to the
      I/O port range, which the kernel translates arch-appropriately.  If
      there is no such file then it'll try to use port instructions if that's
      a thing the architecture has.  So you only need one path, pciaccess
      exists to get the portability right for you.
      
      https://bugzilla.redhat.com/show_bug.cgi?id=1201877
      c1e88427
  20. 07 Apr, 2015 2 commits
  21. 02 Apr, 2015 1 commit
  22. 01 Apr, 2015 2 commits