1. 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
  2. 19 3月, 2010 1 次提交
    • T
      6935821: G1: threads created during marking do not active their SATB queues · 9677603a
      tonyp 提交于
      Summary: Newly-created threads always had the active field of their SATB queue initialized to false, even if they were created during marking. As a result, updates from threads created during a marking cycle were never enqueued and never processed. The fix includes remaining a method from active() to is_active() for readability and naming consistency.
      Reviewed-by: ysr, johnc
      9677603a
  3. 18 3月, 2010 1 次提交
  4. 24 2月, 2010 2 次提交
  5. 17 12月, 2009 1 次提交
    • I
      6862387: tune concurrent refinement further · 7f92f7a2
      iveresov 提交于
      Summary: Reworked the concurrent refinement: threads activation, feedback-based threshold adjustment, other miscellaneous fixes.
      Reviewed-by: apetrusenko, tonyp
      7f92f7a2
  6. 22 10月, 2009 1 次提交
  7. 07 10月, 2009 2 次提交
  8. 03 10月, 2009 1 次提交
    • T
      6885041: G1: inconsistent thread dump · 510d088c
      tonyp 提交于
      Summary: When G1 is enabled, thread dumps are inconsistent as the info for some of the G1 threads is not formatted properly.
      Reviewed-by: ysr, johnc
      510d088c
  9. 01 10月, 2009 1 次提交
  10. 16 9月, 2009 1 次提交
  11. 15 8月, 2009 1 次提交
  12. 20 8月, 2009 1 次提交
    • T
      6871111: G1: remove the concurrent overhead tracker · 228aaca7
      tonyp 提交于
      Summary: Removing the concurrent overhead tracker from G1, along with the GC overhead reporter and the G1AccountConcurrentOverhead (both of which rely on the the concurrent overhead tracker).
      Reviewed-by: iveresov, johnc
      228aaca7
  13. 29 7月, 2009 1 次提交
    • X
      6862919: Update copyright year · 84c0f327
      xdono 提交于
      Summary: Update copyright for files that have been modified in 2009, up to 07/09
      Reviewed-by: tbell, ohair
      84c0f327
  14. 15 7月, 2009 1 次提交
  15. 30 6月, 2009 1 次提交
  16. 24 6月, 2009 1 次提交
    • T
      6850869: G1: RSet "scrubbing" scrubs too much · 502bb88f
      tonyp 提交于
      Summary: RSet scrubbing incorrectly deletes RSet entries that point to regions tagged as "continues humongous" due to a race when RSet scrubbing iterates over regions in parallel.
      Reviewed-by: apetrusenko, iveresov
      502bb88f
  17. 13 6月, 2009 1 次提交
  18. 01 5月, 2009 1 次提交
  19. 17 3月, 2009 2 次提交
  20. 08 3月, 2009 1 次提交
  21. 16 12月, 2008 1 次提交
    • X
      6785258: Update copyright year · f9cf0f22
      xdono 提交于
      Summary: Update copyright for files that have been modified starting July 2008 to Dec 2008
      Reviewed-by: katleman, ohair, tbell
      f9cf0f22
  22. 02 12月, 2008 1 次提交
  23. 21 11月, 2008 1 次提交
    • Y
      6684579: SoftReference processing can be made more efficient · bf0e7f79
      ysr 提交于
      Summary: For current soft-ref clearing policies, we can decide at marking time if a soft-reference will definitely not be cleared, postponing the decision of whether it will definitely be cleared to the final reference processing phase. This can be especially beneficial in the case of concurrent collectors where the marking is usually concurrent but reference processing is usually not.
      Reviewed-by: jmasa
      bf0e7f79
  24. 06 8月, 2008 1 次提交
  25. 11 6月, 2008 1 次提交
  26. 06 6月, 2008 1 次提交