1. 13 Nov, 2018 1 commit
  2. 30 Oct, 2018 1 commit
  3. 26 Oct, 2018 1 commit
  4. 24 Oct, 2018 1 commit
  5. 26 Sep, 2018 1 commit
  6. 19 Sep, 2018 1 commit
  7. 28 Aug, 2018 3 commits
  8. 24 Aug, 2018 2 commits
  9. 23 Aug, 2018 2 commits
  10. 30 Jul, 2018 1 commit
  11. 10 Jul, 2018 1 commit
  12. 05 Mar, 2018 3 commits
  13. 14 Feb, 2018 1 commit
  14. 20 Dec, 2017 1 commit
  15. 02 Nov, 2017 1 commit
  16. 24 Oct, 2017 1 commit
    • Michael Lippautz's avatar
      [heap] Scavenger: Filter pages that are scavenged from sweeper · 9317f8d2
      Michael Lippautz authored
      Avoid locking the pages for the scavenger by filtering out pages that require
      sweeping and scavenging from the sweeper. This way we preserve the assumption 
      that processing slots on a page is sequential. 
      
      Pages that have been scavenged are re-added to the sweeper to allow them to
      be reused for allocation.
      
      CQ_INCLUDE_TRYBOTS=master.tryserver.v8:v8_linux64_tsan_rel;master.tryserver.v8:v8_linux64_tsan_concurrent_marking_rel_ng;master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
      
      Bug: v8:6923
      Change-Id: I7d159de11792ef16a534f29e31791d06d7fb5221
      Reviewed-on: https://chromium-review.googlesource.com/730603
      Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
      Reviewed-by: 's avatarHannes Payer <hpayer@chromium.org>
      Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48859}
      9317f8d2
  17. 17 Oct, 2017 1 commit
  18. 29 Sep, 2017 1 commit
  19. 04 Sep, 2017 1 commit
  20. 30 Aug, 2017 1 commit
  21. 28 Aug, 2017 1 commit
  22. 25 Aug, 2017 1 commit
  23. 27 Jul, 2017 1 commit
  24. 24 Jul, 2017 1 commit
    • Michael Lippautz's avatar
      [heap] Fix Barrier used in Scavenger · 486e641c
      Michael Lippautz authored
      The barrier assumed that the number of tasks is fixed. However, we
      cannot rely on that because other tasks might take up threads. In the
      ein thend this would result in the Scavenge task being (rightfully)
      cancelled.
      
      The barrier now assumes no tasks in the beginning and relies on the fact
      that reaching the barrier means that no global work is left. Tasks that
      lag behing will just observe the barrier being in its end state.
      
      Bug: chromium:738865
      Change-Id: I4d47e8ec4b9cf7c615b3d9585e4a6bb9d271d409
      Reviewed-on: https://chromium-review.googlesource.com/582947Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#46842}
      486e641c
  25. 20 Jul, 2017 1 commit
  26. 18 Jul, 2017 1 commit
  27. 17 Jul, 2017 1 commit
  28. 13 Jul, 2017 1 commit
  29. 12 Jul, 2017 2 commits
  30. 10 Jul, 2017 2 commits
  31. 07 Jul, 2017 1 commit
  32. 06 Jul, 2017 1 commit