1. 18 Nov, 2020 1 commit
  2. 22 Sep, 2020 1 commit
  3. 09 Jun, 2020 2 commits
  4. 23 Apr, 2020 1 commit
  5. 06 Apr, 2020 1 commit
  6. 17 Mar, 2020 1 commit
  7. 28 Feb, 2020 2 commits
  8. 14 Feb, 2020 1 commit
  9. 08 Jan, 2020 2 commits
  10. 03 Jan, 2020 1 commit
  11. 30 Dec, 2019 1 commit
  12. 21 Dec, 2019 6 commits
  13. 16 Dec, 2019 2 commits
  14. 14 Nov, 2019 1 commit
  15. 29 Apr, 2019 1 commit
  16. 11 Apr, 2019 1 commit
  17. 04 Sep, 2018 1 commit
  18. 03 Aug, 2018 1 commit
  19. 31 Jul, 2018 1 commit
  20. 27 Jul, 2018 1 commit
  21. 02 Jul, 2018 1 commit
    • Erik Faye-Lund 's avatar
      gallium/u_vbuf: drop min/max-scanning for empty indirect draws · 4c877057
      Erik Faye-Lund authored
      When building with asserts enabled, we'll end up triggering an assert
      in pipe_buffer_map_range down this code-path, due to trying to map
      an empty range. Even if we avoid that, we'll trigger another assert
      a bit later, because u_vbuf_get_minmax_index returns a min-index of
      -1 here, which gets promoted to an unsigned value, and gives us an
      out-of-bounds buffer-mapping offset.
      
      Since we can't really have a well-defined min/max range here when
      the range is empty anyway, we should just drop this dance in the
      first place. After all, no rendering is going to be produced.
      
      This fixes a crash in dEQP-GLES31.functional.draw_indirect.random.0
      on VirGL for me.
      Signed-off-by: Erik Faye-Lund 's avatarErik Faye-Lund <erik.faye-lund@collabora.com>
      Reviewed-by: default avatarMarek Olšák <marek.olsak@amd.com>
      4c877057
  22. 13 May, 2018 1 commit
  23. 27 Mar, 2018 1 commit
  24. 12 Mar, 2018 1 commit
  25. 06 Nov, 2017 1 commit
    • Marek Olšák's avatar
      gallium/u_vbuf: use signed vertex buffers offsets for optimal uploads · 71f5fe36
      Marek Olšák authored
      Uploaded data must start at (stride * start), because we can't modify
      start in all cases. If it's the first allocation, it's also the amount
      of memory wasted. If the starting offset is larger than the size of
      the upload buffer, the buffer is re-created, used for 1 upload, and then
      thrown away. If the upload is small, most of the buffer space is unused
      and wasted. Keep doing that and the OOM killer comes. It's actually
      pretty quick.
      
      With signed VB offsets, we can set min_out_offset = 0
      in u_upload_alloc/u_upload_data.
      
      This fixes OOM situations with SPECviewperf.
      71f5fe36
  26. 26 Aug, 2017 1 commit
  27. 20 Jun, 2017 2 commits
  28. 10 May, 2017 3 commits