1. 25 6月, 2010 1 次提交
  2. 24 6月, 2010 1 次提交
  3. 22 6月, 2010 1 次提交
  4. 19 6月, 2010 1 次提交
  5. 11 6月, 2010 1 次提交
  6. 10 6月, 2010 1 次提交
  7. 05 6月, 2010 1 次提交
  8. 04 6月, 2010 1 次提交
  9. 30 5月, 2010 1 次提交
  10. 28 5月, 2010 2 次提交
  11. 21 5月, 2010 1 次提交
  12. 20 5月, 2010 1 次提交
  13. 19 5月, 2010 1 次提交
  14. 18 5月, 2010 1 次提交
  15. 17 5月, 2010 1 次提交
  16. 12 5月, 2010 1 次提交
  17. 04 5月, 2010 2 次提交
  18. 02 5月, 2010 1 次提交
  19. 01 5月, 2010 1 次提交
  20. 30 4月, 2010 1 次提交
  21. 23 4月, 2010 1 次提交
  22. 08 5月, 2010 1 次提交
    • T
      6949307: G1: raise a vm error, do not core dump, if target pause time and... · 7a0c8373
      tonyp 提交于
      6949307: G1: raise a vm error, do not core dump, if target pause time and target interval are inconsistent
      Summary: First, change the guarantee to raising a vm error. Second, set the interval dynamically, and based on the pause time target, if it is not set explicitly.
      Reviewed-by: ysr, johnc
      7a0c8373
  23. 16 4月, 2010 1 次提交
  24. 08 4月, 2010 4 次提交
  25. 06 4月, 2010 1 次提交
    • T
      6940310: G1: MT-unsafe calls to CM::region_stack_push() / CM::region_stack_pop() · 1bf17034
      tonyp 提交于
      Summary: Calling the methods region_stack_push() and region_stack_pop() concurrent is not MT-safe. The assumption is that we will only call region_stack_push() during a GC pause and region_stack_pop() during marking. Unfortunately, we also call region_stack_push() during marking which seems to be introducing subtle marking failures. This change introduces lock-based methods for pushing / popping to be called during marking.
      Reviewed-by: iveresov, johnc
      1bf17034
  26. 31 3月, 2010 1 次提交
    • T
      6937160: G1: should observe GCTimeRatio · ba4ccdf3
      tonyp 提交于
      Summary: Remove the G1GCPercent parameter, that specifies the desired GC overhead percentage in G1, and observe the GCTimeRatio parameter instead.
      Reviewed-by: jmasa, johnc
      ba4ccdf3
  27. 19 3月, 2010 1 次提交
  28. 18 3月, 2010 1 次提交
  29. 17 3月, 2010 1 次提交
  30. 16 3月, 2010 1 次提交
  31. 14 3月, 2010 1 次提交
  32. 12 3月, 2010 1 次提交
  33. 11 3月, 2010 1 次提交
  34. 10 3月, 2010 1 次提交
  35. 04 3月, 2010 1 次提交