1. 08 4月, 2010 1 次提交
    • J
      6940894: G1: assert(new_obj != 0 || ... "should be forwarded") for compaction tests · bc7497dc
      johnc 提交于
      Summary: Humongous regions may contain multiple objects as a result of being retained as to-space from a previous GC and then re-used as to-space after being tagged as humongous. These changes include a check that causes retained to-space regions that are now tagged as humongous to be disregarded and a new to-space region allocated.
      Reviewed-by: tonyp, iveresov
      bc7497dc
  2. 06 4月, 2010 2 次提交
    • T
      6909756: G1: guarantee(G1CollectedHeap::heap()->mark_in_progress(),"Precondition.") · 524b2dd2
      tonyp 提交于
      Summary: Make sure that two marking cycles do not overlap, i.e., a new one can only start after the concurrent marking thread finishes all its work. In the fix I piggy-back a couple of minor extra fixes: some general code reformatting for consistency (only around the code I modified), the removal of a field (G1CollectorPolicy::_should_initiate_conc_mark) which doesn't seem to be used at all (it's only set but never read), as well as moving the "is GC locker active" test earlier into the G1 pause / Full GC and using a more appropriate method for it.
      Reviewed-by: johnc, jmasa, jcoomes, ysr
      524b2dd2
    • 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
  3. 03 4月, 2010 2 次提交
  4. 02 4月, 2010 1 次提交
  5. 01 4月, 2010 1 次提交
  6. 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
  7. 24 3月, 2010 1 次提交
  8. 19 3月, 2010 3 次提交
  9. 18 3月, 2010 3 次提交
  10. 17 3月, 2010 3 次提交
  11. 16 3月, 2010 2 次提交
  12. 14 3月, 2010 1 次提交
  13. 12 3月, 2010 2 次提交
  14. 11 3月, 2010 1 次提交
  15. 05 3月, 2010 1 次提交
  16. 10 3月, 2010 1 次提交
  17. 04 3月, 2010 2 次提交
  18. 03 3月, 2010 1 次提交
  19. 02 3月, 2010 1 次提交
  20. 27 2月, 2010 1 次提交
  21. 26 2月, 2010 3 次提交
  22. 25 2月, 2010 1 次提交
  23. 24 2月, 2010 3 次提交
  24. 23 2月, 2010 1 次提交
  25. 20 2月, 2010 1 次提交