1. 23 Oct, 2017 1 commit
  2. 28 Aug, 2017 1 commit
  3. 17 Aug, 2017 2 commits
  4. 14 Jul, 2017 1 commit
  5. 11 Jul, 2017 2 commits
  6. 21 Jun, 2017 3 commits
  7. 28 Apr, 2017 1 commit
  8. 22 Jul, 2016 2 commits
  9. 21 Jun, 2016 1 commit
    • Vinson Lee's avatar
      glx-swap-event: Fix logical-not-parentheses warning. · 1d52edc0
      Vinson Lee authored
      glx-swap-event.c:161:26: warning: logical not is only applied to the left hand side of this comparison [-Wlogical-not-parentheses]
                          if ( ! Intel_swap_event == 0 ) {
                               ^                  ~~
      glx-swap-event.c:161:26: note: add parentheses after the '!' to evaluate the comparison first
                          if ( ! Intel_swap_event == 0 ) {
                               ^
                                 (                    )
      glx-swap-event.c:161:26: note: add parentheses around left hand side expression to silence this warning
                          if ( ! Intel_swap_event == 0 ) {
                               ^
                               (                 )
      
      Fixes: b6a0fc0f ("glx: Add test for glx swap event's receive and its asynchronization.")
      Signed-off-by: Vinson Lee's avatarVinson Lee <vlee@freedesktop.org>
      Reviewed-by: Brian Paul's avatarBrian Paul <brianp@vmware.com>
      1d52edc0
  10. 06 Jun, 2016 1 commit
  11. 21 Apr, 2016 2 commits
  12. 06 Mar, 2016 1 commit
  13. 29 Sep, 2015 1 commit
  14. 10 Jan, 2015 1 commit
  15. 17 Nov, 2014 1 commit
    • Neil Roberts's avatar
      Add a test for GLX_ARB_context_flush_control · 0a3404cd
      Neil Roberts authored
      The test takes the following steps using two threads. The threads are
      only used so it can operate on another context without having to
      rebind it. The threads are run lock-step so that each step is run
      sequentially.
      
      Thread 1: Make a flushless context A
      Thread 1: Make a flushy context B, shared with A
      Thread 1: Make a flushy context C, shared with A
      Thread 1: Bind context A
      Thread 2: Bind context C
      Thread 1: Make a renderbuffer.
      Thread 1: glClear() it to green.
      Thread 1: glFinish()
      Thread 1: glClear() it to red.
      Thread 2: Do a glReadPixels()
      
      (At this point the GL implementation is allowed to have finished
      the clear to red but it probably won't have. If the read pixels
      returns green here then it's not a failure but the test won't work
      so it will report PIGLIT_SKIP)
      
      Thread 1: Bind context C
      Thread 1: sleep(.5)
      Thread 2: Make sure glReadPixels() is still green, otherwise fail.
      
      All of the steps are then run again but this time context A is made
      flushy and the last step ensures that the pixel becomes red instead
      of green. If it did become red then the GL successfully made a
      flush when context A was released.
      
      The test also verifies that calling glGetIntegerv with
      GL_CONTEXT_RELEASE_BEHAVIOR returns the expected value when setting
      the attribute to none and flush and also when the attribute is left
      out entirely.
      0a3404cd
  16. 15 Nov, 2014 1 commit
  17. 14 Nov, 2014 1 commit
  18. 15 Jul, 2014 1 commit
  19. 27 Jun, 2014 1 commit
    • Jasper St. Pierre's avatar
      glx-swap-event: Make sure that swap events are on the correct drawable · fe3ba4d6
      Jasper St. Pierre authored
      DRI2 had a bug in its implementation which caused the
      GLX_BufferSwapComplete event to be emitted for the X11 Drawable,
      instead of the GLXDrawable instead, as the specification for
      INTEL_swap_event says should happen.
      
      This didn't happen for indirect GLX contexts or for DRI3, which properly
      sent out the GLXDrawable inside the code. Since userspace already relies
      on getting the X11 Drawable, we are fixing the spec and mesa to be based
      around the X11 Drawable instead.
      
      Make sure that the event has the X11 Drawable in its drawable field.
      
      Corresponds to mesa commit b4dcf87f34f68111acd9d364739938721fc692f4
      Signed-off-by: Jasper St. Pierre's avatarJasper St. Pierre <jstpierre@mecheye.net>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      fe3ba4d6
  20. 26 May, 2014 1 commit
  21. 13 Mar, 2014 2 commits
  22. 19 Jan, 2014 1 commit
  23. 26 Oct, 2013 1 commit
  24. 03 Oct, 2013 2 commits
  25. 25 Jul, 2013 1 commit
    • Frank Henigman's avatar
      new test: glx-multithread-texture. · cd9ca682
      Frank Henigman authored
      New test for loading texture data from one thread and context while drawing
      with those textures from another thread and shared context.  The threads are
      synchronized so they do not attempt to use the same texture at the same time.
      
      v2
      - use MIT license
      - fix formatting
      - correct float pixel value is integer/255, not integer/256
      - may not have alpha channel, so don't probe it
      - sleep to prevent starvation
      - passes on pineview with intel driver and nvidia
      
      v3[chadv]
      - fix build by passing api to piglit_dispatch_default_init()
      Signed-off-by: default avatarFrank Henigman <fjhenigman@google.com>
      Tested-by: Brian Paul's avatarBrian Paul <brianp@vmware.com>
      Reviewed-by: Brian Paul <brianp@vmware.com
      cd9ca682
  26. 18 Jul, 2013 1 commit
    • Jose Fonseca's avatar
      glx-multithread-shader-compile: call XInitThreads. · ab46f1d0
      Jose Fonseca authored
      Prevents the test from aborting when testing Mesa XLib state tracker as:
      
        [xcb] Unknown request in queue while dequeuing
        [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
        [xcb] Aborting, sorry about that.
        glx-multithread-shader-compile: ../../src/xcb_io.c:179: dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq' failed.
        Aborted
      
      And it matches what glx-multithread.c does.
      
      Trivial.
      ab46f1d0
  27. 17 Jun, 2013 1 commit
  28. 12 Jun, 2013 1 commit
  29. 24 Apr, 2013 1 commit
  30. 19 Mar, 2013 1 commit
  31. 01 Mar, 2013 2 commits